Hi Mark. Would this process be any different in reverse? As in, the trigger is on a child record, and then I'd like to trigger a search of parent records, and then create records for each parent record *not* returned in the search.
My existing pipeline (not using bulk upsert) was flagged and shut down for excessive use today when bulk importing historical data. Seems like I need to find a less intensive method.
------------------------------
Ken Hillyer
I support people who cure cancer
Alliance for Clinical Trials in Oncology Foundation
Boston, MA
------------------------------
Original Message:
Sent: 12-06-2021 11:11
From: Mark Shnier (YQC)
Subject: Bulk Record Sets in Pipelines
That make request step is not necessary. I think they just confuse their example with a more complicated example of trying to do two things for each record found in the search. In your case it sounds like you want to trigger on a change in the parent record, create your bulk upsert box, do your search and then for each add a bulk record row and then the last step will be to commit the upsert.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
Original Message:
Sent: 12-06-2021 10:12
From: Christine White
Subject: Bulk Record Sets in Pipelines
Thanks! Do you know how that "make request" step here is supposed to be set up? (This example is essentially what I am trying to create) https://help.quickbase.com/pipelines/about_bulk_record%20sets.html?Highlight=bulk
------------------------------
Christine White
Original Message:
Sent: 12-06-2021 09:06
From: Mark Shnier (YQC)
Subject: Bulk Record Sets in Pipelines
If the trigger is on a parent record and you want to trigger a search of children and create records for each child record returned in the search then yes a bulk record upsert would be perfect for your needs.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
Original Message:
Sent: 12-06-2021 08:41
From: Christine White
Subject: Bulk Record Sets in Pipelines
This is on a Trigger from the "Project Tag" table. So thought the Bulk Record Set would essentially perform the "loop" function for me? Never used it before.
------------------------------
Christine White
Original Message:
Sent: 12-06-2021 08:37
From: Mark Shnier (YQC)
Subject: Bulk Record Sets in Pipelines
Would this be running on a schedule or on a trigger? If on a trigger and they are just getting added one by one then you don't need to use a bulk record set.
If the trigger is some mass operation line an import or a grid edit, then a bulk import would be better to use. But I don't think you need to use the Make Request Step.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
Original Message:
Sent: 12-06-2021 08:34
From: Christine White
Subject: Bulk Record Sets in Pipelines
I have a "Project Tag" Parent Table allowing users to Group projects as needed. I would like to create a new record in a Request table for each of these Child projects and thought I could use the Bulk Record set feature for this.
------------------------------
Christine White
Original Message:
Sent: 12-06-2021 08:23
From: Mark Shnier (YQC)
Subject: Bulk Record Sets in Pipelines
Can you explain what you are trying to do? Maybe you don't need that step.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
Original Message:
Sent: 12-06-2021 07:47
From: Christine White
Subject: Bulk Record Sets in Pipelines
I would like to build a pipeline using the Bulk Record feature. My scenario is similar to the example here https://help.quickbase.com/pipelines/about_bulk_record%20sets.html?Highlight=bulk. I am not clear on the "Make Request" Step. Wondering if I can get additional details or if there a video available on this feature?
------------------------------
Christine White
------------------------------