Solved
Using arguments with "Call Another Pipeline" function
I have been working with QB tech support to no avail on this one. I have created a pipeline to create a series of nested folders on Box.com. The list of folders to create has grown to over 30 in num...
- So in a complete turnaround, I was later told by Quickbase support the exact opposite of what I was told in my first two inquires: Passing arguments between Pipelines does in fact work, and it works perfectly for my use case. I only wish it hadn't taken me an entire week of pulling teeth out of multiple support reps to get a correct answer.
I now have a multiple pipelines chained together by passing the target record ID (and more) to the subsequent pipelines. The nicest advantage I have realized from this is the ability to have multiple variations of my "Step 1" pipelines, with various triggers, and have them all continue to one unified "Step 2" pipeline that has the same chain of actions for all cases. That means you can easily augment the trigger and initial actions without have to rebuild/duplicate the long chain of following actions that result.
I will attempt to upload the screencast that was shared with me that shows how to do it.
------------------------------
Josh Weeman
------------------------------
