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.
Is it possible to chain workflows together, passing the results of one to another?
For example, I have a workflow that I want to reuse to process several different input files. The files are all Excel workbooks with different formats (different column headers and data types).
What I want to do is create a different workflow for each of these incoming formats. Those workflows would "standardize" the format and datatypes and then pass the resulting data set to the main workflow that finishes the process.
I have looked at the Chaining Workflows Together article here, but the Crew Tools do not appear to accept a dataset as an input for the new workflow.
Am I going about this the wrong way? Do I need to output the "standardizing" workflow dataset first and then use that as an input for the new workflow? Is there a completely different approach I should take for this task?
(I am brand new to Alteryx and just looking for a little guidance). Thank you!
If curious, our use case is this:
We received production reports from several different companies, all reporting similar data that we need to combine into one standard output format. Each of those companies has their own reporting structure. I basically like to drop each of these reports into a workflow and have Alteryx extract the data from it and build a report that matches our target formatting requirements. Once that is done, pass it off to another workflow that processes reports in that target format.
Since you seem to know how many different formats you have coming in, perhaps you could nest IIF statements to alias the needed fields for your main processing. It would just seem that different modules to accommodate your pre-processing would be more cumbersome in the long run.
If you do choose to maintain separate "formatting" runs prior to main processing, you may want to incorporate an Event (click on the canvas, look at the config window) that will run your processing module once you have preprocessed your customer file. You will call the alteryx engine.exe, and indicate the directory path to the module to run upon completion w/o errors.
It's assumed that once you have created your pre-processing output, that is being uniformly named so that you can address it with a directory tool and a dynamic input tool to read in the file.
Hopefully that will give you a few options to get started down a path.
Say I have App01, which has Output01. And say I have App02, with Input01, but Input01 IS actually Output01.
What you'd want to do is take App01 and chain App02 to it. And send App01 up to the Gallery, but when you do, go into the Manage Assets section, and include Output01 as an asset that you're sending, as well as App02.
What will happen is when you run App01 in the Gallery, it will complete by (a) created Output01 in its own little temp space, and then (b) fire off App02 which will use that Output01 in the temp space as Input01.