Discussions

Expand all | Collapse all

Using arguments with "Call Another Pipeline" function

Jump to Best Answer
  • 1.  Using arguments with "Call Another Pipeline" function

    Posted 05-15-2020 13:44
    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 number.  This is a problem since the maximum number of steps a pipeline can have is 30.  So the only viable workaround that has been suggested so far is to call a second pipeline at the end of the first pipeline, and finish my routine in the second pipeline. In theory that would work, except that QB tech support now tells me there is no way for me to pass the record ID of the target QB record to the second pipeline, even though the (extremely limited) instruction that accompanies the "Call Another Pipeline" function clearly states you can pass arguments.  If you can't pass something as fundamental as a record ID as an argument to the second pipeline, how can it perform any sort of targeted action? Any if the arguments won't allow for passing a QB record ID, what WILL they allow and why do they even exist?

    Has anyone successfully used this function with arguments?  TIA.

    ------------------------------
    Josh Weeman
    ------------------------------


  • 2.  RE: Using arguments with "Call Another Pipeline" function

    Posted 05-15-2020 16:41
    I don't have a direct answer to passing arguments between pipelines but a workaround would be to create a single record in a single table with record ID# = 1 and have a pipeline write some values to that rcord field.
    Then you can look that up down to any child table you need.
    This can work as long as you are fairly sure that you would not have multiple pipelines are running at the same time and tripping over Each other as they write onto that scratchpad field.  


    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------



  • 3.  RE: Using arguments with "Call Another Pipeline" function

    Posted 05-15-2020 17:53
    Great suggestion Mark, thanks. Pretty sure I can come up with work around based on that, but you're right, would be troublesome in a scenario where we might have multiple instances of the pipeline being fired off around the same time.

    Got an update from QB tech support: According to the pipeline developers, the ability to pass an argument between pipelines doesn't exist, despite the instruction text below the "Call another pipeline" object that attempts to explain how to do it. Surprising that they jumped the gun and published a reference to a feature that hasn't even been developed yet.

    ------------------------------
    Josh Weeman
    ------------------------------



  • 4.  RE: Using arguments with "Call Another Pipeline" function

    Posted 05-15-2020 18:11
    Well the positive spin about that, is that at least they must be planning for it to happen at least.

    I just discovered that an Automation can access the Record ID# of a previous Add Record Step. Never knew that and they say its been there all along.

    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------



  • 5.  RE: Using arguments with "Call Another Pipeline" function
    Best Answer

    Posted 06-05-2020 12:02
    Edited by Josh Weeman 06-05-2020 12:06
    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
    ------------------------------



  • 6.  RE: Using arguments with "Call Another Pipeline" function

    Posted 02-18-2021 17:28
    Josh I just wanted to say thank you for this quick video, it got me past a hurdle and opened up a whole world of possibilities!  I used Callable Pipelines to iterate over multiple paged results from a JSON request.  I passed the page number argument through from a "Calling" pipeline to the pipeline that actually made the request to the other app's API.  

    ie "https://gitlab.com/api/v4/groups?page={pagenumberfromcallingpipeline}"

    ------------------------------
    Brian Richardson
    ------------------------------