What's new in Fundraising and Engagement May 12, 2021
This Fundraising and Engagement update (v1.2.3.0) affects both the Dynamics 365 solution and Azure services. It contains the following updates:
| Updated item | Description |
|---|---|
| Gift entry | Improved one-time gift entry, reducing the time to process a donation by at least 30%. |
| User interface | Improved the user interface to better match a gift entry user's mental model for entering required information, enabling quicker and more accurate gift processing. |
| Enhanced constituent research via LinkedIn to help prospect researchers take advantage of features like Get introduced, Icebreakers, and embedded communication. | |
| Visual Studio | Visual Studio is no longer required during database migration. |
| Dynamics 365 data push model | Replaced the Dynamics 365 data push model with an Azure data polling model, ensuring Azure-initiated pulls are secured with managed identity. |
| Stripe Service Key | Increased the length of the Stripe Service Key field in the msnfp_PaymentProcessor entity to 510 characters. |
| Redesigned forms | Redesigned the Transaction, Donor Commitments, and Payment Schedule forms. Most the forms use Unified Interface. The forms now feature the following Power Apps component framework controls:
|
| Date format and currencies | Date format and currencies abide by Dynamics 365 language pack rules. |
| Anonymous donations | When you select an anonymous donation, a new anonymous record is no longer created. Instead, the transaction is associated with a contact record and marked as anonymous. Future functionality will allow for easier reporting. |
| Membership | A membership can only be added to a one-time transaction. We hope to expand this functionality in the future to distribute a membership over multiple recurring payments. |
| LinkedIn integration | Fundraising and Engagement and LinkedIn Sales Navigator integration is now live. Review the LinkedIn Sales Navigator Installation Guide for details on the integration. |
Be sure to update your environment to the newest release (v1.2.3.0) for both Dynamics 365 and Microsoft Azure Services.
Update instructions
Application users representing the Azure services provisioned in Dynamics need to be assigned a new field security profile Fundraising and Engagement Azure App User. Follow the instructions in Assign field security profile to the application user.
You need to generate a new app registration client secret to access Dynamics 365 from Azure services. You must delete the old key.
Clear the value of the deprecated Azure Web API URL field. Navigate to Configuration area > Configurations, clear the value of the Azure Web API URL field, and save changes.
More information
The terminology for Fundraising and Engagement App registration ID and client secret changed.
Crm Application ID is now referred to as Fundraising and Engagement App registration application (client) ID.
Crm Application Key is now referred to as Fundraising and Engagement App registration client secret.
The respective ARM template parameters are renamed to AppRegistrationClientId and AppRegistrationClientSecret.
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.