Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesWe have a need to be able to trace the lineage of fields being processed through Alteryx - and it has to be done at a field level to satisfy our regulator. In essence, we have to be able to show exactly where a particular field came from, and demonstrate that we can trust this field. NOTE: If we could do this - then we could also use this information to make EVERY canvas faster, by checking for unused fields and making suggestions to remove these unused fields early in the flow.
In order to do this - it would be great if there were an option to force explicit field names in the Alteryx XML so that we can trace a specific field.
cc: @AdamR_AYX @jpoz @Claje
Example:
Here's a simple canvas:
- 3 fields coming in from an input
- Select tool with these 3
- output of three fields into a file
These three fields are not mentioned anywhere in the XML
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.