Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more 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

Ability to explicitly control the order of operations of Output tools

If you have either of these situations: 1) a series of dependent database outputs (as in database-supplied auto-incrementing IDs needed for subsequent Inserts/Updates) or 2) writing a file that is used later in a workflow (as in a Run Command call or an R script), you need a way to guarantee tools that don't have outputs themselves (like the Output Tool) are complete. I believe this use case is fairly common.

If the Input tool had an (optional) input stream and the Output tool had an (optional) output stream, you could fully incorporate them into workflows, including use of Block Until Done. I know there are some alternative solutions to make this work, but they are not intuitive.

2 Comments
PoornimaF
Alteryx Alumni (Retired)
Hi Dan,

Thanks for the suggestion. We are actually improving Block Until Done to make the use cases that you describe more intuitive for the upcoming Alteryx Analytics 10.0 release. We believe that this would be more optimal as opposed to adding multiple, optional input or output stream within the Input or Output tool respectively that might confuse the user. Please reach out to Products if you would like a demo.

Thanks,
Poornima
TaraM
Alteryx Alumni (Retired)
Status changed to: Implemented