Archived
AttributeHider
+40- Contributor
The opposite of the attributeExposer. Sometimes I need to temporarily expose an fme_attribute in order to preserve it's value (ex. LineJoiner) or replace it's value (ListIndexer), but would rather not have it trailing through the rest of the workspace, especially when this takes place within a custom transformer.
+22- Safer
We've been talking about adding this into the new AttributeManager at some point.
In teh meantime, you can put down a PythonCaller -- by default it does nothing -- and you can use its "hide attributes" to accomplish what you want. Awkward and annoying I know. But at least you can do it already.
+11- Contributor
Too bad that it hasn't made the cut in the past 8 years. I wanted to post exactly this idea today. You got my vote!
I know you can use a PythonCaller or TCLCaller as a workaround, but it doesn't feel ideal. Also, isn't it the case that using a PythonCaller (by default) would break bulk mode? That, next to loading in dlls (packages/modules) don't feel to be neccessary for what we would like to achieve.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.