Skip to main content
Solved

FME 2025 SpatialRelator removes Requestor attributes (BUG?)


kalbert
Supporter
Forum|alt.badge.img+14

@safe I just recognized that the SpatialRelator in 2025 does not release my Requestor attributes as before (2024 and any older version I remember).

I’m used to use the SpatialRelator with the setting ‘Generate List’ checked (incl. some selected attributes) and keeping the ‘Merge Attributes’ unchecked. As a result I see all my Requestor attributes and where applicable the list attributes according to the spatial relation I’m looking for.

Now in 2025 the above setting ONLY releases the list attributes and all my Requestor attributes are removed. The only way to bring it back is to check the ‘Merge Attributes’ checkbox as well, which is not my intention.

I guess it’s a bug since the Transformer page still states for ‘Output’: These are the Requestor features with the new attributes added. One list entry is made for each of the Suppliers that has at least one matching predicate.

 

FME Form 2025.0 build 25208

Best answer by DanAtSafe

Hi ​@kalbert and ​@takashi I’ve filed FMEENGINE-86533 about the SpatialRelator where Requestor attributes are unexposed if they’re not merged with the Supplier’s.

View original
Did this help you find an answer to your question?

5 replies

takashi
Influencer
  • April 8, 2025

Hi ​@kalbert ,

Looks like the attributes of Requestor features wouldn't be propagated to Output features, but in my observation, internally still exist, just disappeared on Workbench canvas. You can see those attributes on Feature Information window - Unexposed Attributes section.

In the interim, you can use AttributeExposer to re-expose the hidden attributes.

@DanAtSafe, I think it's a kind of bug, can you please file this? 


DanAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • Best Answer
  • April 9, 2025

Hi ​@kalbert and ​@takashi I’ve filed FMEENGINE-86533 about the SpatialRelator where Requestor attributes are unexposed if they’re not merged with the Supplier’s.


nielsgerrits
VIP
Forum|alt.badge.img+54

Can someone at Safe set up a test workspace in FME 2025 to check all transformers on this behaviour? This also happened with some other transformers and is a pretty significant issue. I’m a bit  anxious about this release as we will be implementing it and I’ll be tied to this version for the coming 3 years.


takashi
Influencer
  • April 9, 2025

I agree with Niels' suggestion.

In my experiences, FME version YYYY.0 tends to contain serious bugs every year unfortunately, so I do not use YYYY.0 in production.

Although pricing of FME productions has been increased with the rebranding 2023, the quality control doesn't seem to be improved so much. I strongly hope Safe Software will enhance quality control on a new version of FME, especially on the first one of each year before releasing.


kalbert
Supporter
Forum|alt.badge.img+14
  • Author
  • Supporter
  • April 9, 2025

Hi all,

thanks for feedback. It seems I found a severe issue. So looking forward to 2025.0.2

The Lizard has some work to do ;-)


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings