v1.2.1 – RaiseNow Digital Fundraising Kit for Dynamics 365 nonprofit accelerator

This release requires the RaiseNow Fundraising Kit for Dynamics 365 nonprofit accelerator v0.1.2 in conjunction with our backend release v1.2.1. 

If you are already using v0.1.2of our Fundraising Kit for Dynamics 365 nonprofit accelerator we will upgrade your integration automatically to the latest backend integration. 

If you are still using a prior version, please contact support to schedule the upgrade. You can find the solution attached to the article for download and installation. Additionally, you will find an Excel sheet attached in the article for data mapping from RaiseNow to Dynamics 365 Nonprofit Accelerator.

Support for Twint Reconciliation for Hub Payments

This release introduces support for reconciliation for Twint payments submitted via the RaiseNow Hub. For customers using the RaiseNow reconciliation service, individual payments will be automatically updated in Dynamics when the summary payout is received in the organisations bank account. 

Individual msnfp_transactions records in Dynamics will be updated with:

• rnw_raisenowfees
• rnw_acquirerfees
• rnw_netamount
• statecode : 0 
• statuscode -> according to the defined statuscode map for your organisation
• rnw_acquirername
• rnw_acquirertransferidentifier
• rnw_acquirertransactionidentifier
• rnw_reconciliationreportidentifier
• rnw_recipientbankaccount

Support for attachments to transfer your custom data points to Dynamics

You can now configure your touchpoint to send relevant data that may not be included in the standard RaiseNow field set to Dynamics. The data will be added as a note on the created commitment. The implementation differs slightly between the new Hub platform and the legacy RaiseNow Manager platform. In Dynamics you can use custom workflows to process the data according to your requirements. See this article in our knowledge base for details. 

Example from RaiseNow Manager

Example from RaiseNow Hub:

Further bug fixes and improvements

• Resolved errors tied to NULL values in custom parameters.
• Removed specific validations in the Hub payment status code handling to future-proof against new status code introductions.
• Fortified the notification message system to counter unexpected or absent data entries, ensuring no notification goes amiss.
• Enhanced validation checks for 'BirthDate' and incorporated error-handling to exclude incorrect values without disrupting processes.
• Implemented a filter to scrub illegal characters in entity names, especially when linking with the Dynamics deduplication endpoint. Problematic characters are now auto-cleaned from all requests.