Hey @HA,
As @ThizViz mentioned, you can do this in different ways if you're thinking about the zero-row issue (in other words - only write the files if there's more than 0 rows in each file).
Options I can think of are:
- Instead of writing them to file at the end of each branch of the workflow; you can write them to a database (or Alteryx file), and then in the next workflow you pull the data out and only generate outputs if there are >0 rows in both sets.
- Append the record count from each set to the other data set - and then filter this field for >0. This means that you won't write either file if either stream has zero rows
Note: You can do things in steps by wrapping them in Batch Macros - and then creating a canvas that brings all these batch macros onto 1 canvas.
For example - one batch macro to generate this data; another to do the writing. That way, you can have the benefit of having 1 workflow and still divide this into steps.
If the worry you have is that a file may fail to output because of disk space or something else - then you're going to need to do something after the write to check.
Options:
- tie a batch file to event on the end of the workflow (in workflow events) - which deletes either if the other doesn't exist
- do the same batch macro - but execute it in a Run command in a set of dependant macros like the note above.
:-) If these help to solve your problem, please mark this as solved to close this thread out @HA
Thank you
Sean
