What's new in Fundraising and Engagement February 04, 2021
This Fundraising and Engagement update (v1.0.0.5) mitigates the following issues:
| Issue | Mitigation |
|---|---|
| Recurring web job scheduling | Fixed an issue with recurring donations web job scheduling. The web job now runs once per 24 hours, at 4:00 AM. Action required: To apply the Azure fix, refresh your local copy of the Fundraising and Engagement GitHub repository, and redeploy the recurring donations web job. |
This release also includes the following updates:
| Updated item | Description |
|---|---|
| New role | A new role called FundraisingandEngagement: Azure App User was introduced for application user connections used by Azure services. This new role allows users to store Azure connection information more securely. Action required: To apply the latest security features of Fundraising and Engagement, it's necessary to assign the new role to the application user used by Azure services.
|
| Name field | The Name field of the msnfp_Configuration entity is now writable so users can name their configuration records. |
| Error logging | Improved error logging for generic errors in the Dynamics 365 plugin to make troubleshooting easier. |
| NullReferenceException | Fixed NullReferenceException with the msnfp_donorcommitmentid field in the TransactionGiftCreate plugin and updated the version attribute in the Dynamics 365 plugin. This bug appeared in the APAC region last week after a Dynamics 365 platform update prevented users from completing transactions. We expect the change to be pushed out across all regions, so be sure to update to assure transactions continue to work as designed. |
Important
Users with access to Fundraising and Engagement may work with sensitive data. We recommend that administrators and users enable multifactor authentication to increase the security of their environment.