Join the Alteryx Community’s Maveryx Summer Cup event! Compete, network with others, and earn your gold through a series of challenges from July 24th to August 11th. Learn more about the event here.
The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Full field description in XML - Verbose mode option

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)

cc: @AdamR_AYX @jpoz @Claje 



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




20 - Arcturus
20 - Arcturus

@SeanAdams I like it!  Would you also want to include this lineage into connect product?  With PII and sensitive data would you have any additional needs?  




17 - Castor
17 - Castor

Absolutely yes @MarqueeCrew  - we do want automatic field level lineage in Connect to bring this product up to base capability with other commercial data catalogs on the market. 


And as you imply - having the fields in the XML is the enabling step.

7 - Meteor

@SeanAdams not a solution but an attempt to address one of the "side benefits" of what you're proposing:

Alteryx Community Team
Alteryx Community Team

We appreciate your idea and feedback! We strive to improve our product and insure our users are being heard. Make sure to check out our Submission Guidelines and check out ideas submitted by other users and the other idea boards.