Skip to main content
Best answer

Zeffy to Salesforce Issue: Overwriting fields and not recording on campaign

  • September 27, 2024
  • 4 replies
  • 73 views

Forum|alt.badge.img

Task is to accept Donation payment via ZEFFY and move that into Salesforce for Non Profits (NPSP).

I created a ZAP to migrate actual payments made through ZEFFY for Non-Profits.  I have the Connection to ZEFFY working perfectly and get the payment data to test with and move into Salesforce NPSP.  

My logic looks for New Donation vs Recurring Donations and then does an update of the Donation record and also Updates the Payment record.

Problem I have is after updating the Donation/Payment records is that it overwrites the Rollup total fields with that last payment information on Contact, Account, Donation records and does not update Campaign record even when I pass the Campaign name..

ASK: Does anyone have an example that takes Payment or Donation information from a tool like ZEFFY then updates Salesforce via ZAP  and updates correctly the rollup total fields on Contact, Account, Donation, Payment and Campaign totals?

Appreciate any guidance or examples I can test with to figure out the flaw in my logic or what I am missing.

Thank you

Bill A.

Best answer by Bashton_TXBest answer by Bashton_TX

My source data from Zeffy presents exactly as I am expecting it.

  1. Had not thought of the batch process delay as a possible cause for not updating the rollup fields.   ACTION: Will test it again and allow sufficient time to complete those jobs before checking.
  2. My initial logic was updating the Donation and Payment records (See image below) but will add updating the Campaign record  by ID as well.

 

 

Thank you for your guidance

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 2633 replies
  • October 1, 2024

Hi @Bashton_TX,

 

Welcome to the Community.

 

Salesforce NPSP updates rollup fields through scheduled batch jobs, which may cause delays in showing correct totals after a Zap runs. For Campaign record updates, ensure you pass the record ID, not the name. A typical Zap setup involves searching for or creating Contacts and Campaigns, updating Donation and Payment records, and reflecting changes in Contact and Account records. Testing each step is crucial, and be aware that rollup fields might not update immediately due to the batch processing schedule.


Forum|alt.badge.img
  • Author
  • Beginner
  • 5 replies
  • Answer
  • October 1, 2024

My source data from Zeffy presents exactly as I am expecting it.

  1. Had not thought of the batch process delay as a possible cause for not updating the rollup fields.   ACTION: Will test it again and allow sufficient time to complete those jobs before checking.
  2. My initial logic was updating the Donation and Payment records (See image below) but will add updating the Campaign record  by ID as well.

 

 

Thank you for your guidance


JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 2633 replies
  • October 2, 2024

Hi @Bashton_TX,

 

It’s fantastic that your Zap is working now as intended. If you have any questions, feel free to ask us here in the Community.


Forum|alt.badge.img
  • Author
  • Beginner
  • 5 replies
  • October 3, 2024

Thanks for the guidance.

I have it working now for One-time New Donations where it updates the Donation, Contact, Account, Payment and Campaign records, including correctly updating the rollup totals on each of the objects. 

 

I will be adding/testing more logic for Recurring Donations and also a path test to check if a SalesForce record exists, if not will create one then continue down the donation path to record the donation details.

 

Below is the current working one time New Donation flow where I combined Generating both the new Donation and Payment in the same step with the flag DO_NOT_CREATE_PAYMENT flag set to FALSE forcing the Payment record to be created at the same time: