I have a screen flow on a campaign page that a user can run to tag all related opportunities (Donations actually, this is NPSP) for further processing, which will be thank-you letters in Apsona. It basically just un-checks a checkbox on all donation records that are checked from last time, then checks the same checkbox for all donations related to the current campaign.
I have an on-update flow that normally runs when a donation record is updated, but I DON'T want it to run when that screen flow causes all those updates.
When the number of donations gets too large, I end up with
Apex CPU time limit exceedederrors.
Any thoughts? Thank you!
I wanted to come back and close the loop on this (one of my pet peeves is when people leave issues open, or worse, close it out with "I figured it out" and NOT provide details for others who come along!).
Because that particular checkbox field is used exclusively for this purpose, I added the following entry condition to the "big flow" that typically runs every time a donation (opportunity) record is created or updated.
Condition: Formula Evaluates to True
NOT( ISCHANGED({!$Record.For_Apsona_Merge__c}))
#Apsona
