Forum Discussion
MarkShnier__You
Qrew Champion
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
------------------------------
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
KenHillyer
2 years agoQrew Member
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
------------------------------
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
------------------------------
- MarkShnier__You2 years agoQrew Champion
I suggest that you make a field on the Parent called [Parent Exists? With a formula of true.
then lookup down to child.
Then trigger pipeline on child created and [Parent Exists?] is no.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------