Dynamics MS Nonprofit Accelerator Integration v2.1.0
This release provides support for updating payment schedules in Dynamics. In addition, data points for community fundraising with the Koalect platform are provided.:::
Highlights in this release:
This update requires installation of the RaiseNow solution in v1.0.1, which can be downloaded here. Customers need to install the solution and contact RaiseNow Support to initiate the backend upgrade.
Process payment schedule updates
This release provides support for processing deactivation and re-activation of payment schedules. The new version of the solution registers webhooks with dynamics so RaiseNow can automatically process updated payment schedules in dynamics. Future updates will provide support for changing installment schedules and amounts.
For RaiseNow Hub subscriptions the deactivation will be interpreted as a suspension of the corresponding subscription in RaiseNow. Re-activation of the payment schedule also re-activate the RaiseNow subscription.
For RaiseNow Manager subscriptions, deactivation of the payment schedule must be interpreted as a cancellation of the corresponding subscription in the RaiseNow Manager. This is necessary, as the RaiseNow Manager does not support suspension of subscriptions. A re-activation of the subscription in the RaiseNow Manager will also re-activate the corresponding payment schedule.
Remove rnw_fundraiserid and introduce rnw_fundraiser_id
This breaking change removes the rnw_fundraiserid lookup field from the data model shipped with our solution. The intention of the field was to link the acquiring fundraiser with a donation. However, this feature was not used in any production context and it did create problems for some customers. Hence, it was removed.
For future use cases a new field was introduced: msnfp_donorcommitment.rnw_fundraiser_id. This field is defined as simple string field and is intended to be used as an external (non-unique) identifier.
Pass payment reference to Dynamics
It is now possible to pass payment references with RaiseNow transactions to Dynamics. For example, if you construct a Swiss QR code for a touchpoint solution, with a payment reference,
Example:
https://donate.raisenow.io/[solution-key]?reference.qr=100100000000000000001002762
the created msnfp_transaction in Dynamics will have the corresponding file value on msnfp_transaction.rnw_paymentreference.
Though this is primarily intended for the use with Twint QR codes, this method will work for all Hub payment methods. For RaiseNow subscriptions, every payment record in RaiseNow will be created with that reference. Subsequent msnfp_transaction records in dynamics for the corresponding gift commitment will also be created with that reference.
It is possible to leverage this method for RaiseNow Hub payments created through Tamaro as well but this does require some customization in Tamaro. In addition this process will not work for payments created through the RaiseNow Manager platform. Please consult customer success if you intend to use it in this manner so our team can advice on implications.