What's new in Fundraising and Engagement June 30, 2022
This Fundraising and Engagement update (v2.0.3.3) mitigates the following issues:
| Issue | Mitigation |
|---|---|
| Potential for the first payment of a recurring donation to be charged twice | We updated the time zone, time, and date stamping logic in the payment schedules to align to the payment transaction of recurring donations. These improvements now ensure that recurring payment transactions aren't double charged. |
| Inconsistent behavior on Next Payment Date of certain recurring donations | We introduced improvements to ensure that the next payment date of a recurring donation is updated to the correct date, time, and time zone. These improvements ensure that the recurring donation is automatically processed per the logic the user initially defined. |
This release also includes the following payment and transaction updates. Be sure to update your environment to the newest release (v2.0.3.3) for both Dynamics 365 and Microsoft Azure Services.
| Updated item | Description |
|---|---|
| Payment schedule page | The dates now correctly display in the user’s time zone as set in the user settings. In prior releases, a single time zone per tenant was displayed and used to define the logic of a recurring donation’s automated payment process. |
| Payment Schedule entity | Start Date, End Date, Next Payment Date, and Book Date are changed in the user interface to ensure consistent display logic for users in the same time zone. |
| Transaction entity | Book Date, Deposit Date, Received Date are changed in the user interface to ensure consistent display logic for users in the same time zone. |
| Contact entity | Last Transaction Date are changed in the user interface to ensure consistent display logic for users in the same time zone. |
| Recurring Donation jobs | These jobs now run once per day at 4:15 AM UTC by default. You can change this setting. |
| Recurrence Start in recurring donations | This field now displays only when Time Period is Month and is relevant. |
| Book Date [msnfp_bookdate] on Payment Schedule form | Book Date defaults to the current date of the end user’s time zone when a transaction is created, unless the user sets another date The time portion of Book Date is automatically set to midnight (00:00:00) in the user’s time zone. Date and time are converted and stored in UTC time zone through background Dynamics 365 services. Users continue to see Book Date as a date-only field in the user interface. The Book Date timestamp remains hidden in the user interface. |
| Start Date [msnfp_firstpaymentdate] on Payment Schedule page | When created, the field defaults to the current date and time of the end user’s time zone. If the user selects a different date, the related time stamp is updated to midnight (00:00:00) in the user’s time zone. Date and time are converted and stored in UTC time zone through background Dynamics 365 services. Users continue to see Start Date as a date-only field in the user interface. The Start Date timestamp remains hidden in the user interface. |
| End Date [msnfp_endondate] on Payment Schedule page | Where a date is selected, the time defaults to 23:59:59 in the user’s time zone. Date and time are converted and stored in UTC time zone through background Dynamics 365 services. Users continue to see End Date as a date-only field in the user interface. The End Date timestamp remains hidden in the user interface. |
Important
Users with access to Fundraising and Engagement may work with sensitive data. We recommend that administrators and users enable multi-factor authentication to increase the security of their environment.