We are celebrating the 10-year anniversary of the Alteryx Community! Learn more and join in on the fun here.
Start Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Need Suggestion - Condition based Workflow branches

Faisal___28
7 - Meteor

have a use case - where I have around 30 different statement of accounts from our vendors - So I have created a seperate workflow for each of them to extract the relevant data and have a common named columns for all of them. So later I can append them all into a single sheet and have some analysis run (filter/join) with my internal reports. 

Now I want to make this dynamic where in move this to Alteryx app and have the user upload the SOA and get the clean outcome and then run the analysis - but each Statement of account has a different workflow and the correct workflow should run based on filename so now using filter tool I mapped the correct WF branch and now these to be unioned and then my analysis to be run.

 

Now when I published it to server and try to run im getting the attached errors. Please anyone worked on a similar use case can help me out. 

Faisal___28_2-1755684698276.png

 

 

 

 

 

Faisal___28_1-1755684350336.png

 

 

 

10 REPLIES 10
WirkKarl
7 - Meteor

Hi Faisal,

It sounds like you’re on the right track with branching workflows based on filenames. A couple of suggestions that might help:

  1. Use the “Detour” or “Conditional Runner” tools: Instead of multiple filter tools for each workflow, you could route files dynamically using a single conditional branch or the “Detour” macro, which often simplifies unioning later.

  2. Check file naming consistency: Make sure the uploaded filenames exactly match your mapping logic. Even small differences (extra spaces, capitalization) can cause the workflow branch to fail.

  3. Debug on server: Sometimes workflows run fine locally but fail on the server due to path or permission differences. Use a log or write a temporary output to see which branch is actually being executed.

  4. Union carefully: When unioning outputs from multiple branches, ensure all column types and names match exactly. Mismatches often cause errors on server runs.

If you haven’t already, consider wrapping your conditional branches in a batch macro — this often makes dynamic filename-based processing much smoother when moving to an app on the server.

Labels
Top Solution Authors