Could there be an option/setting/toggle that would analyze workspace at start of run for the optimal place to "kill" or drop any attributes which are not ultimately get written or used to derive some other value beyond a certain point? That way they are still shown as available at every stage in the workspace so that the author has full access to them. This would increase run performance because those attributes don't get (cached/processed) beyond where they are needed while also sparing the author from having to add/configure the attribute keeper transformer, which can cause additional headaches later as the workspace evolves and you suddenly need that attribute you dropped somewhere earlier. Could call it the Dynamic Orphaned Attribute Killer workspace parameter, jk.
Archived
Setting to dynamically drop any abandoned attributes during run
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
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.