When inspecting features that have filtered user attributes, only show the attributes selected in the reader/in the workflow in the Feature Information Window. The Table View does this currently - could it be implemented for the Feature Information view as well?
Archived
Removing Attributes from Feature Information Window in Data Inspector
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.
+26- Contributor
I think marking them as "not exposed" or "hidden" would be a better idea. That way you can still determine if any "not exposed" attributes are available on the feature.
Good Idea, but I think the expected filtering functionality should be optional and all the attributes including hidden ones should be shown by default.
In addition, it might be convenient if the Attributes section in the Feature Information would be split into:
two sections - User Attributes and Format Attributes,
or three sections - User Attributes, Format Attributes (Format Specific), and Format Attributes (FME Generic).
+63
I like the idea, but maybe implement it in a similar fashion to the Workbench feature type reader attribute list, like @takashi says: all shown by default with the option to hide them.
Maybe make lists collapsible as well in the feature information window?
+5- Contributor
Adding to the ideas here, I think an option to present the feature information attributes sorted to match the order inside transformers would go a long way to making it easier to work with.
A text filter where you can quickly trim it down to to the attribute you're after would be great, ideally with multiple values somehow, and history to quick pull up the recent filter values.