Pipeline Design for Bulk Record Updates
Hi all. I have a timecards table where users track all the things they're working on. Relatedly, we have a separate child timecard table, with a narrower field list but otherwise the exact same recor...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendThe purpose of the On New Bulk event is to ensure that records are processed one by one and don't overwhelm the system and also in use cases where you really want the first record processed before you start processing the second. A small example of that would be where child records are being created in bulk and sometimes they need a corresponding parent record created. If you do not use Bulk Trigger you will get multiple pipelines running simultaneously and both trying to create the same unique parent record. One will fail and generate errors.
But you are right, in terms of performance, Bulk Triggers is going to make the process run slower.
If this is important to you and you can scrounge up some budget for outside consulting, I'm pretty sure that Sharon Faust (Quickbase Junkie) can help you.
A while back Sharon did a Qrew Demo where she used advanced techniques in Pipelines with Jinja which allowed her to achieve a 10x or maybe 100x speed up in processing speed.
interesting, thanks Mark. Sounds like I misunderstood the purpose of the bulk event step. So for updating thousands of records all at once, it's still easiest/most performative to just have the pipeline loop through all the records one at a time (outside of leveraging Sharon's self-created methodology)?