What's new in Fundraising and Engagement December 12, 2023
Important
Fundraising and Engagement is being retired. Support for Fundraising and Engagement will end at 11:59 PM Pacific Time on December 31, 2026. For more information, go to What’s new in Fundraising and Engagement.
Microsoft Tech for Social Impact is proud to announce the December 12, 2023 release of Fundraising and Engagement. This release brings significant enhancements mainly to nonprofit gift processors. This release includes valuable enhancement Fundraising and Engagement Azure services.
New features
The December release of Fundraising and Engagement includes the following new capabilities:
Likelihood to donate AI model: The likelihood to donate AI model helps you understand which of your contacts are likely to donate soon. This forecast helps nonprofit marketers and fundraisers create new segments of donors to tailor their outreach based on this likelihood, sometimes referred to as propensity. For more information, go to Determine who's likely to donate soon.
French language availability: If French language is enabled in your organization, you can select it as User interface language or Support language in Dynamics 365 personalization settings.
Improvements in donor and opportunity management:
- Various screens are updated to modern Dynamics 365 components for ease in customizations and improved usability.
- Opportunity pages are streamlined for quick editing and easier navigation.
- Household address updates are more flexible and all field changes are transparent.
- Common transaction actions are moved to the ribbon. For example, converting a donor commitment to a donation or charging the first payment of a recurring donation.
Configuration of Stripe tokenization method
- The Fundraising and Engagement solution includes a new capability to payment processing using the Stripe payment gateway integration. This capability ensures that payment processing with Stripe payment processor can use the new Payment Intents API.
- This integration preference of the Stripe Payment Intents API is optional. You can set it up based on your payment processing needs. To take advantage of the new Stripe Payment Intents API integration, we added a toggle called PaymentIntentEnabled to Fundraising and Engagement Azure services Key Vault.
Note
If you turn on the Stripe Payment Intent API, it seamlessly works with the existing payment tokens in the application. However, after you turn on this integration, any newly created cards won't be compatible with the previous payment processing method. If you want to revert to the previous payment setup, be aware that newly added cards won't function with the older system.
Deprecated features
The Designation field (msnfp_designatedcredit_designationid) that is an attribute on Designated Credit is an unused duplicate and is deprecated.
The following components are deprecated from Fundraising and Engagement and replaced with improved components. They're still available under the Deprecations solution that is included in the package in case you want to use them for your own customized component.
| Component | Reason for deprecation |
|---|---|
| Accounthouseholdtile.html | Legacy component that is no longer visible |
| Contacthouseholdtile.html | Legacy component that is no longer visible |
| Msnfp_cancelecurringdonation.html | Functionality moved to the ribbon |
| Msnfp_charge_donation_now_button.html | Functionality moved to the ribbon |
| Opportunitydesignation.html | Replaced with improved component |
| Opportunityexistingpreferences.html | Replaced with improved component |
| Opportunitypreferences.html | Replaced with improved component |
| Opportunityreportingplan.html | Replaced with improved component |
| Opportunitystages.html | Replaced with improved component |
| Solicitation.html | Legacy component that is no longer visible |
| Updatehouseholdaddress.html | Replaced with improved component |
| Writeoffpopup.html | Replaced with improved component |
| Msnfp_convert_to_donation_button.html | Functionality moved to the ribbon |
Updates
This release includes the following updates:
| Description | How it worked before | How it works now |
|---|---|---|
| Removing payment processor | When user removed the payment processor, it was removed from Dynamics 365. | If the payment processor is removed, it's removed from both Dynamics 365 and Azure. |
| Deactivating a payment method | User received an error when trying to deactivate a payment method. | User can successfully deactivate a payment method. Note: You can't reactivate deactivated payment methods. |
| Converting a pledge to donation including membership amount | Membership Amount was intermittently counted twice when converting a pledge to donation. | The Membership Amount shows correctly on the donation form. |
| Merging contacts | User received an error due to the execution time threshold. | User can successfully merge the contacts without getting an error. |
| Donation import - accessibility | User couldn't see the values on the dropdown when trying to import a donation. | User can see all dropdown values. |
| Donation import - household | When user imports a donation record related to an existing donor and household, the import process ignored the donor and household relation. | Donor, household, and donation records are all linked correctly after the donation import process. |
| Donation import - household | When user imports a donation record related to a new donor, the import process automatically linked the donor and transaction with a household, although the household wasn't provided in the import file. | Donor, household, and donation records are all linked correctly after the donation import process. |
| Transaction - print thank you | The print thank you action gave the error: "The given key wasn't present in the dictionary." | Users can print thank you for the transactions without receiving an error. |
| Transaction - description length | The msnfp_TransactionDescription attribute had a different maximum length on Azure and Dynamics 365. Users had issues on lifetime giving total value calculations due to this mismatch. | The maximum length of the Azure TransactionDescription field is updated to 250 characters to match the field length in Dynamics 365. |
Important
Fundraising and Engagement is comprised of Dynamics 365 and Azure services. We highly recommend that nonprofit organizations and partners upgrade both Fundraising and Engagement Dynamics 365 solution version 2.3.3.0 and Azure services to version 2.3.3.0 to take advantage of the latest improvements.
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.