span8
span4
span8
span4
Idea by denniswilhelm · · expose attributesattribute handlingattributeexposer
I think it would be very handy if you could expose attributes from the feature cache. The main idea is that you would run a workspace once to build up your cache and use these features to get a list of possible attributes to be used in the AttributeExposer.
Especially when using a PythonCaller or a HTTPCaller that retrieves an arbitrary JSON structure, this would allow you to easily identify all required attributes.
What do you think?
annabelleatsafe commented ·
Hi @denniswilhelm,
Thanks for posting!
This ties in to (a very popular!) idea posted here: https://knowledge.safe.com/idea/18842/bulkattributeexposer-expose-all-possible-attribute.html — Namely, "I would like an AttributeExposer that can optionally auto-populate with all available attributes when running the workspace. In other words, a transformer that scans the schema and adds all found attributes to the list (when set to 'record option'). Excluding fme_ and schema attributes would be helpful".
The main idea being, "As a user, please populate transformers with known attributes so that I can avoid having to manually type/remember attributes from upstream in my workflow". If this also captures your requirements, please vote there and I will consolidate these ideas to better reflect the demand for this functionality.
Share your great idea, or help out by voting for other people's ideas.
Add an "Attributes to expose" parameter to AttributePivoter
Add option to immediately rename exposed attributes
Add "exposer" to AttributeManager
Aggregator: missing option to not accumulate attributes or use only base
Setting to dynamically drop any abandoned attributes during run
Autoconnect attributes on multiple links
Support field indexing in GEODATABASE_FILE writer
Add attributes sequence in reader and writer
Transformer that Exposes all Attributes when Working with Dynamic Workflows
© 2019 Safe Software Inc | Legal