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 t...
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 ------------------------------
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
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 ------------------------------
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.