It sounds a lot like an issue I reported to Safe back in november:

“… attributes that were renamed by a BulkAttributeRenamer were unexposed after passing through a FeatureTypeFilter if the Update button was used to populate the list of feature types. If the feature type name was added manually there was no issue and everything worked as it should.”

That was filed as FMEFORM-32399 by ​@DanAtSafe 

I very recently heard something similair from a teammember (attributes being unexposed after a transformer in 2025) but I have not been able to reproduce it. Happy to hear it is already reported!

Ah this is different. We found the PoinOnLineOverlayer unexposing attributes. Sample attached. Ticket submitted.

​@nielsgerrits Unfortunately merged attributes were unexposed in the PointOnLineOverlayer, PointOnAreaOverlayer and LineOnAreaOverlayer. These issues were recently fixed via FMEENGINE-86065; I’ll let you know when the fix is available to download.

Hi ​@kalbert Are you using a FeatureTypeFilter after the BulkAttributeRenamer? If not, please submit a case via safe.com/support

​@redgeographics The “problem” you saw with the FeatureTypeFilter was intentional as of FME 2022.0 Some users had requested that feature type output ports honor the original Feature Type settings. We could consider adding an option for the user to pick the behavior they want. 

Hi ​@DanAtSafe I submitted a case. The attribute removal I’ve reported has nothing to do with any following transfomer.

​@kalbert FYI, the problem with the BulkAttributeRenamer in FME 2025.0+ has been filed as FMEENGINE-86480.  We’ll let you know when it’s been fixed.