This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We 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.
Alteryx currently only makes a note of a field name if it is changing that field which is very economical - but it makes tracing fields impossible.
Desire is for every tool to write the field list to the XML definition for every field that it knows about (just like it looks in the UI)