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
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)?
MarkShnier__You
Qrew Legend
Qrew Legend.... Yes, aside from Sharon, you should be using the Bulk Step and maybe you don't really care if it takes hours and hours to run because your app will still "Performative" (running nicely) for your regular users.
A very nice design feature of the Bulk Trigger and the Regular Trigger is you can set the number of records for it to trigger on.
So for example, you can set the Regular one to trigger when a maximum of 1 record is updated or created, and that will ensure that your manual entry users still get instant processing. And then you set the Bulk Trigger one to to trigger at 2 or more records being changed.
When I went looking for that setting on the regular trigger for On New Event, in an older Pipeline, the setting at the bottom of the box for the maximum number of records to trigger on, was not there. I was initially confused so I started to build a brand new pipeline and that same On New Event trigger did have the new setting at the bottom of the box. So you may have to go back to your existing regular On New Event trigger and replace it the same so that it will have that new feature.