I was asked by some admins to come up with a demonstration of setting a contact lookup field on opportunity to that of the the primary donor contact role. Here is my solution. What issues do you see? And do you have ways to solve some of the shortcomings?
1) Setup PB to run each time an opportunity it created or edited. Calls flow passing in opportunity ID.
2) Flow gets primary contact role and copies corresponding contact ID to a custom picklist field Primary_Contact.
This seems to work fine upon the following situations:
o creating a new donation using the UI
o editing the donation using the UI
o updating the donation through Apsona (but batch size must be less than 100)
o importing donations through Apsons (but batch size must be less than 100)
I have proven that this runs only once during NPSP 3.0 for the above situations.
It fails to update if you change the primary donor contact role from one to another role, if you add a brand new primary control role, or if you delete the primary contact role. Apparently these are not changes to the opportunity.
Finally, there are limits apparently to how many times a flow can do things to the database when invokes in batches. So you have to keep batch size under 100 to avoid failures one would normally see if you have a flow the looped and queried the database too many times.
Many admins want this type of contact lookup field for receipting. I guess it's available in one or two of the not-NPSP platforms build on Sf. I'm even considering it myself so that I can accomplish receipt generation fully native.
#receipt #flow #process builder @Salesforce.org System Administrators
Thanks @Terry Cole for posting about this. And thanks to @Judi Sohn - I was just wondeing this morning how to get that primary contact on the Opportunity.
