Discussions

 View Only
  • 1.  Automation to pipelines

    Posted 10 days ago
    Hi, 

    I am trying to migrate an existing automation to pipelines. The problem is the automation includes more than 26 steps. All the actions in automation is adding a record to a certain table and that step repeats 49 times. In other words, Add record 1, add record 2, add record 3.....add record 49. Is there a way to optimize the existing automation to reduce the number of steps to below 26 and migrate to pipelines?

    Or is it better to build a new pipeline and how do I build a new pipeline with steps less than 26 but at the same time add 60 records or more.

    Any help will be appreciated.

    ------------------------------
    Bibhav Rimal
    ------------------------------


  • 2.  RE: Automation to pipelines

    Posted 10 days ago
    Can you explain what these child records represent? One way to do this is to have a helper table which includes these records to be added. Then have a single pipeline step which will do a table to table import copying those records as records into the target table.

    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------



  • 3.  RE: Automation to pipelines

    Posted 10 days ago
    Hi Mark, 

    These records are adding parts and quantities. 

    Trigger: add a record to X table with A and B is checked.
    Action 1: Add a record (part 1 and quantities 1) to Y table.
    Action 2: Add a record (part 2 and quantities 2) to Y table.
    Action 49: Add a record (part 3 and quantities3) to Y table

    ------------------------------
    Bibhav Rimal
    ------------------------------



  • 4.  RE: Automation to pipelines

    Posted 9 days ago
    Are these records being added to a parent record as child records?
    Like this is a Project and based on the Project Type you need a certain set of Child records Created?

    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------



  • 5.  RE: Automation to pipelines

    Posted 4 days ago

    Let's say we are building a house in Site A

    There are 3 tables to consider;

    1. Activities table
    2. Parts master list table and
    3. Build parts table.

    Whenever a record is created in the activities table the automation pulls the parts needed for that building in site A from the master list and populates it in the build parts table. Now if I want to add 49 parts, I can do so by going to the activities table and I can pick the parts and quantities I need for that building. I cannot add more than 49 parts because of the limitation of the automation. So if there are 100 parts I can only add 49 parts at a time. 

    I want to migrate this automation to pipeline but there are more than 26 steps and I cannot migrate to pipelines. I am looking for an efficient way to optimize this automation to less than 26 steps.

    I was reading about callable pipeline. will it work in this situation?

    For each part I want to add there are different steps. 



    ------------------------------
    Bibhav Rimal
    ------------------------------



  • 6.  RE: Automation to pipelines

    Posted 4 days ago
    I suggest that you consider not using Pipelines or Automations to individually add the parts list.

    Instead, make a table of Standard House types - in fact maybe you already have this table which would select from when you create an Activity.  Create a child table to that table called Standard Build Parts.   The standard build parts would be selected off a relationship from the Parts Master.

    The set up a pipeline to trigger when a House Type is selected and the Activity has no child build parts as yet.

    The Pipeline will trigger and the search the Standard Build parts table for those parts which match the House Type.  Then have a "For Each" loop to create the child Build parts records.

    The advantage of this method,  of course, is that you can easily maintain the standard build parts  for any Standard House Type, the Standard Build Parts are easily visible to users,  and creating new House Type with their own sets of standard bill parts is easy without having to modify the Pipeline.

    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------