Skip to main content
Solved

During Using FeatureTypeFilter Update the _relationship attribute lost.

  • July 14, 2025
  • 6 replies
  • 280 views
omerseyfettin
Contributor
Forum|alt.badge.img+9

When a database is updated using SpatialRelator, FeatureTypeFilter, and DatabaseUpdater Transformers from feature classes inherited from two different readers, the _relationship attribute disappears when the FeatureTypeFilter Update button is used. All DatabaseUpdater transformers are in the "incomplete transformer" status. When examining the DatabaseUpdater transformers, the _relationship values are red. Copying and pasting the same value fixes this. To avoid this issue, you must manually edit the FeatureTypeFilter, which is time-consuming.

 

 

Best answer by desiree_at_safe

Hi ​@omerseyfettin 

Thank you for sharing those screenshots! I was able to reproduce what you're experiencing with the FeatureTypeFilter and the disappearing _relationships{} attributes.

I can see you've already identified the current workaround which is manually typing in the feature type names instead of using the Update button. You're absolutely right that this is tedious, especially when working with multiple feature types.

I'm going to escalate this with our development team to hopefully prioritize a solution.

Thank you for bringing this to our attention! 🙂

[INTERNAL NOTE: FMEFORM-28567]

ÖSK

    6 replies

    desiree_at_safe
    Safer
    Forum|alt.badge.img+20

    Hi ​@omerseyfettin,

    That definitely sounds frustrating, especially having to manually fix each of those attribute references!

    Would you be willing to share what version your use and screenshots of your workspace setup, particularly around the SpatialRelator, FeatureTypeFilter and DatabaseUpdater transformers?

    Even better would be a sample workspace if you're able to create a simplified version that demonstrates the issue. Seeing the specific configuration would help me and the community better understand what's happening with those relationship attributes.

    Happy to dig into this with you! 🙂

    Happy FME-ing!
      omerseyfettin
      Contributor
      Forum|alt.badge.img+9
      • omerseyfettinContributor
      • Author
      • Contributor
      • July 16, 2025

       

      Hi ​@desiree_at_safe 

      Already i am  using 2025.1.0.0 (20250704 - Build 25606 - WIN64) last version.

       

      ÖSK
      desiree_at_safe
      Safer
      Forum|alt.badge.img+20

      Hi ​@omerseyfettin 

      Thank you for sharing those screenshots! I was able to reproduce what you're experiencing with the FeatureTypeFilter and the disappearing _relationships{} attributes.

      I can see you've already identified the current workaround which is manually typing in the feature type names instead of using the Update button. You're absolutely right that this is tedious, especially when working with multiple feature types.

      I'm going to escalate this with our development team to hopefully prioritize a solution.

      Thank you for bringing this to our attention! 🙂

      [INTERNAL NOTE: FMEFORM-28567]

      Happy FME-ing!
        desiree_at_safe
        Safer
        Forum|alt.badge.img+20

        Updating the community on this fix, delivered in a recent FME release!

        The FeatureTypeFilter now has an Attributes to Output option, which includes:

        • Source Only > only attributes from original readers (the previous behavior)

        • Source and Added > preserves both original reader attributes and attributes added by transformers in the workspace

        This should help retain the _relationship attribute and avoid that manual workaround. Please download FME 2026.1+ for this fix from our downloads page:

        FME Downloads - Latest Version

        Thank you again for flagging this! 

         

        --

        [internal: FMEFORM-28567]

        Happy FME-ing!
          omerseyfettin
          Contributor
          Forum|alt.badge.img+9
          • omerseyfettinContributor
          • Author
          • Contributor
          • May 12, 2026

          This is great news, but I made this request almost a year ago. At that time, version 2025.1.1 was available and I was using it. Now I'm using 2025.2.4.1 and this feature hasn't been announced in that version. The company has to pay for version 2026.1, which isn't fair.

          ÖSK
          desiree_at_safe
          Safer
          Forum|alt.badge.img+20

          Hi ​@omerseyfettin!

          I hear you. Waiting for a fix and then finding it sits behind another upgrade and cost is genuinely frustrating, and I don't want to gloss over that.

          I'd definitely recommend reaching out to your account representative. They're better positioned to have a conversation about your company's licensing options and what might be available to you.

          I'm glad the fix is in and that your original report helped get us here! We appreciate your patience throughout this process.

          Happy FME-ing!

          Community Stats

          32,644
          Posts
          123,902
          Replies
          41,035
          Members
          Terms & ConditionsAccessibility statement
          A product of
          Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.