What is the expected mapping behavior of custom Recurring Donation fields to Opportunities when installment auto-creation is disabled
?
For example, I want to map a custom 'Acknowledgment Status' field on the Recurring Donation to the 'Acknowledgment Status' field on Opportunities. If NPSP were set to auto-create the next installment, the Recurring Donation's Acknowledgment Status would get mapped to the new Opportunity. However, we have installment auto-creation disabled. So if the next won installment for a Recurring Donation comes in, say, through an online donation platform, would its Acknowledgment Status be inherited from the Recurring Donation:
- When it's created?
- In a batch overnight?
- At all?
- And would the Recurring Donation's Acknowledgment Status get copied to all child Opportunities, or just new ones after the field is updated?
Thank you for any insight you can provide!
#NPSP #Enhanced Recurring Donations #Nonprofit Success Pack #NonprofitHelp #Nonprofit #Recurring Donation
Hi Adam,
The custom field mapping is applied when NPSP creates an installment Opportunity from the Recurring Donation.
So if Installment Opportunity Auto-Creation is disabled, NPSP won't automatically create the next installment just to apply the mapping. If an Opportunity is later created by an external donation platform, the Recurring Donation → Opportunity custom field mapping would not automatically populate that Opportunity unless the integration/process creating it explicitly applies the value.
Also, updating the Recurring Donation doesn't simply copy the value to every historical/closed Opportunity. NPSP's behavior around existing open installment Opportunities can update mapped values depending on the Recurring Donation processing/configuration.
For an online donation platform creating the Opportunity directly, I'd recommend checking the integration's field mapping or automation rather than relying on the NPSP Recurring Donation mapping.
