Use Case: Master Table vs Pipeline?
I am new to Pipelines and also new to Master Tables and would like community guidance: Use Case: We have a complex Project Management Tracking System built in QuickBase. (400 projects, 150 users...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendThis should be done with a Pipeline. If you have never done your first Pipeline, this is a perfect use case to plunge in and learn.
The Trigger should be "On Event" as opposed to Record Created. That will give you the flexibility to trigger on the Project being edited in case for some reason you wanted to manually trigger.
The next step will be to Create a Bulk Upsert. That's like a big old temporary cardboard box to throw stuff into. The reason for this method is that the fastest processing and least impactful on your app performance will be to fill the box outside of QuickBase and then "upsert" the box all at once. You will define the Bulk Upsert by specifying the columns to be populated including the important field for Related Project.
The next step will be to search for records in the master Tasks table which meet some criteria filter or perhaps just get them all. Then after the Search there will be a For Each step where you will Add Bulk Upsert Row ... filling the box. Those fields can be filled by dragging the fields from the right panel, mostly from the search step C but at least one, the Record ID#, from the Step A trigger record.
Then you drag across the last step which will be to Commit the Upsert, ie upload them to the tasks table.
Remember to turn it on and leave that screen open so you can watch it run. Then flip to another tab, create a project and quickly flip back to watch the pay by play unfold as the Pipeline is triggered.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
The Trigger should be "On Event" as opposed to Record Created. That will give you the flexibility to trigger on the Project being edited in case for some reason you wanted to manually trigger.
The next step will be to Create a Bulk Upsert. That's like a big old temporary cardboard box to throw stuff into. The reason for this method is that the fastest processing and least impactful on your app performance will be to fill the box outside of QuickBase and then "upsert" the box all at once. You will define the Bulk Upsert by specifying the columns to be populated including the important field for Related Project.
The next step will be to search for records in the master Tasks table which meet some criteria filter or perhaps just get them all. Then after the Search there will be a For Each step where you will Add Bulk Upsert Row ... filling the box. Those fields can be filled by dragging the fields from the right panel, mostly from the search step C but at least one, the Record ID#, from the Step A trigger record.
Then you drag across the last step which will be to Commit the Upsert, ie upload them to the tasks table.
Remember to turn it on and leave that screen open so you can watch it run. Then flip to another tab, create a project and quickly flip back to watch the pay by play unfold as the Pipeline is triggered.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------