#Recurring Donation0 discussing

I can't figure out how to configure which fields appear when a user creates a new Recurring Donation. In "Setup | Object Manager | Recurring Donation", I have checked all Page Layouts and Lightning Record Pages and none have the fields as they are displayed. What could I be missing? Where else can I configure which fields are displayed? 

Note that the weird layout occurs regardless of how the Recurring Donation is created - using the New button on the "Contact | Recurring Donations" related list or using the New button in the Recurring Donations tab. 

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! 

We observed the below error message : 

Error #1: 

Error Type: Batch Apex error

Error Date: 2025-01-29 21:00:10

Message: "First error: No such column 'npsp4hub__Mandate__c' on entity 'npe03__Recurring_Donation__c'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the a..."

Context: npsp__RD2_OpportunityEvaluation_BATCH 

I am able to see the lookup field Mandate from the NPSP packages, when I access the object in the object manager I am unable to find. 

Since I am unable to find the "npsp4hub__Mandate__c" in the Object Manager, I am unable to Map this field in Recurring Donations, can anyone let me know if there are any suggestions. 

Hi, 

I would like to be able to report on my sales pipeline, including pledged future donations that are recurring. However, the way NPSP is set up means that not all opportunities are created when the recurring donation is set up and I can't accurately report on the sales pipeline. I also can't report on installments. 

If anyone knows of a solution or a way around this, please let me know! 

Thanks, 

Maeve 

I'm the admin for an NPSP org. I set up a NPSP recurring donation with the owner as Unger (not myself) I would expect that all installments would be owned by him. They aren't I always have to go in and change it manually. This is frustrating since I also do fundraising and when it comes to who owns which donations it can get confusing. 

Often our donors fulfill pledges by multiple payments. I know how to break the Opportunity up by Payments. However, if the donor makes open ended recurring payments and wants to apply them to the open pledge, how can I apply these to the Pledge Opportunity in Salesforce so that the Contact record doesn't show a doubled/inflated Donation History?

Also our board has a Give/Get obligation. So if they get someone to donate an amount, (yes, soft credit) but instead is it possible to apply the separate donation as a payment against the open pledge? Or some way to apply the Soft Credit as a payment against the pledge? 

#Nonprofit  #NPSP

Sometime in the last few months, our iATS recurring donations have stopped syncing to Salesforce properly. All existing recurring donations no longer automatically update in Salesforce when a payment is processed. One recurring donation created in September works fine.

I have worked with iATS, and they say that it is an flow trigger issue on the Salesforce side. I am not aware that we made any developer-level changes in that time period. Are other iATS users having this issue, and was there a change on the Salesforce side that could have caused this issue?

I am currently working with a nonprofit organization on some contract work. They use NPSP. I am working through their upgrades and wanted to see if anyone has any experience with the following:

Most of their donations are recurring and come through PayPal. They are looking for a way to automate the import of transactions from PayPal to SF. They tried using Zapier but PayPal support informed them that this is not possible with recurring donations.

I am still looking into the issues but any feedback or guidance would be much appreciated! Thanks!##