Skip to main content

Fundraising Kit for Salesforce NPSP v1.38.1 - Backend Upgrades V1.19.3

[Release Date March 22 2024]

This update provides a bugfix for correctly setting the close date on Opportunities in Salesforce when processing camt files.

tip

Backend upgrades are deployed automatically to all customer installations that meet the minimum requirements. This update requires the installation of the RaiseNow Digital Fundraising Kit v1.38 from the Salesforce AppExchange. Contact RaiseNow support for the installation link.

Set Opportunity close date according to value date from processed camt file​

Update v1.19.0 provided extensive improvements in the processing of camt files. In the course of those improvements, the close date of the Opportunity was set to the processing date of the payment by RaiseNow. Though this is the correct behaviour when processing real time payment methods such as credit cards, for payments generated from processing camt files the closed date must be set according to the value date as reported by the bank. This backend provides an improvement to set the Opportunity Closed Date according to the value date processed from camt files for payment methods:

  • sepa_dd (SEPA Direct Debit)
  • ch_ta (Lsv+)
  • ch_dd (PostFinance Debit Direct)
  • bank_transfer

An additional fix was applied to ensure that the Closed Date was not updated in the course of the settlement reconciliation process.

Catch edge case for payments referencing Recurring Donations that caused duplicate Opportunities to be created​

This update addresses an edge case that caused a duplicate Opportunity to be created, if the Business Process Reference (Payment Reference), referenced both a Recurring Donation and an existing Opportunity in Salesforce. The behaviour was now changed to ensure that the Opportunity with the oldest Closed Date for the given Recurring Donation is selected.

If the RaiseNowBusiness_Process_Referencec object does not reference a Recurring Donation but does reference an existing Opportunity with StageName "Closed Won", a new Opportunity will still be created.

Support multiple occurrences of the same reference number in same payment collection batch​

With the introduction of unpersonalized campaign references, the same reference now frequently occurs multiple times in the same camt file. If multiple occurrences of the same reference were processed in the same batch during bulk processing of those payments, only the first occurrence of a reference was processed. This bugfix solves that issue to ensure all payments and references are processed correctly.