The image below is part of my current workflow, which works as initially desired.
The far left dynamic input returns 29 records and the summarize tool reduces it down to 22 due to duplicates.
Passes the 22 records to the dynamic input for a sql db call, adds a new field, passes the 22 records to another dynamic input for another sql db call, adds an additional field then continues on. For an initial run this does 44 total calls to the database, which I expect. The result is written to a sqlite table further down the flow (not shown in image).
To reduce the calls to the db on additional tests I wanted to add a check against the sqlite file so I added a join tool. Where they join (J) use sqlite data. Where they do not join (L) continue to process as described above. This works up until there are no records getting passed to the process above. If the join has 22 records coming from the dynamic input/summarize side and matches all from the sqlite side the workflow errors with "Both left and right inputs must have connections" error
In the image below I remove the initial dynamic input and replaced it with a text input and text input to simulate the sqlite.
I have attempted an at least 10 times to make a flow that works for all potentials and each one fails when no record is getting passed to the process. I get the following error.
The ask is to get the workflow to run the process when the left side of the join has records and not run the process when the left side does not have records.
Your thoughts are appreciated.
Puff
Solved! Go to Solution.
Hi @stapuff106
I think the Detour tool is a nice way to get this.
https://help.alteryx.com/20213/designer/detour-tool
@Aguisande It's funny you mention the use of the Detour tools. I made up a macro example last week for the first time, but hadn't considered it for this because I was hyper focused on solving it within the workflow (non macro).
Puff
@Aguisande I was able to build the detour. Not a fan of needing to build a macro to handle it, but it works. Something that should be handled in a standard workflow.
Puff
@stapuff106. Hi, can you provide some details on what detour and how you were able to solve this scenario.
Appreciate it thanks.
User | Count |
---|---|
107 | |
82 | |
69 | |
54 | |
40 |