Thanks Kelly & Mark! I ended up using parts of each of your solutions.
I created a helper table called "Blank Records" with 500 empty entries. Then used a pipeline to grab the [# of Suites] from the "Buildings" table and used that to search for "Blank Records" with a RecordID# < [# of Suites]. That returns a list the same size as [# of Suites] to run a loop on. Within that loop I added a bulk upsert row. Finally after the loop completes, I commit the upsert.
Qrew LegendOK, great that you got it working. But if you're looking for some real fun and are willing to invest five minutes, try duplicating your pipeline and hack away everything except the trigger and the search step.
Then insert a step after the search for import to Quickbase.
I think you'll find that find that it runs about 10 times faster. So in a worst case if you had 500 suites, I bet it would take way more than a minute to complete your way with the loop. But I'll bet the Import to Quickbase isn't really sensitive to the size of the number of suites being created and will complete in about five seconds.
It also saves you the set up of creating the bulk upsert and then they add row step and then the final Commit. So in future Pipelines you build, it seems simpler to just go directly to the Import to Quickbase directly after the Search.
Oh that's even better and such an easy change. I've never used (or even noticed) that import to quickbase action. Now I'll need to go through all my pipelines to see where I can use this.
Thanks!
