Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHey all,
We have a policy (similar to the best practices guide published recently by the Copenhagen user group - thank you @danielbrun2) that Alteryx canvasses should run without warnings.
However - some of the warnings are tremendously painful to track down. For example - a union that brings together 20 or 30 input streams which gives you a warning saying "not all fields contain field X".
Can we change this to multiple warnings saying "Input X does not contain field X" so that we click straight through to the offending warning?
Additionally - when there's a conversion error - we then have to run the flow again with filters and diagnostics to find the offending row. Can we have a way that alteryx automatically sidelines an example row so that you can solve it in one pass?
If we look at all the warnings with the intention of "how do we make this something that can be solved right now, without having to run complex diagnostics, so that the very next run is 100% clean" that would be a big help.
Thank you Sean
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.