Troubleshoot Fundraising and Engagement
This article lists known issues, error messages, and tips to help you troubleshoot Fundraising and Engagement in Microsoft Cloud for Nonprofit.
Common issues
Fundraising and Engagement doesn't work with Dynamics 365 Sales Pro
Fundraising and Engagement has a dependency on Dynamics 365 Sales Enterprise. If you try to deploy it into a Dynamics 365 Sales Pro environment, won't have access to important entities, because the Sales Pro license is limited to 15 custom entities. For more information about licensing, go to Dynamics 365 Licensing Guide.
The configuration record and security roles control visibility
If a user runs into an issue where they can’t see parts of the system or the web resource forms appear not to work, check to make sure that the component is configured properly in the configuration record. Ensure the user has the proper security roles. For details on the configuration record and the security roles, go to Security roles.
Receipts, thank-you letters, and invoices require a pre-configured Dynamics template
Throughout the system, there are opportunities to generate physical receipts, thank-you notes, and invoices. These functions will only work if you've pre-configured a Dynamics template in your environment. Without a pre-configured template, nothing happens when you select those options.
For information about pre-configuring these templates, go to Create a template.
During a donation import, use the donation import template
The donation import template maps directly to Fundraising and Engagement. Dynamics import templates standardize data entry and ensure that you can only enter values that will be accepted by Fundraising and Engagement. If you use a .csv import, which isn't recommended, no validation occurs. For more information about donation import templates, go to Create a donation import template.
When processing a transaction or payment schedule, processing doesn't complete
In this case, the processing message doesn't finish and the record isn't created.
Transaction and payment schedule record processing requires a payment processor to be set up on the user's configuration record. Each configuration record requires at least one payment processor, and each user requires one configuration record. For more information about payment processors, go to Set up a payment processor. For more information about configuration records, go to Configure Fundraising and Engagement.
The payment processor entity is required, whether or not you're using an integration to the payment gateway. If a payment gateway isn't available, the payment gateway field is optional and not required. For more information about payment gateways, go to Configure Fundraising and Engagement.
Nothing happens when selecting Process on a new transaction
To process new transactions, you need to configure two items:
- A configuration record for the user
- A payment processor for the configuration record
Note
A payment processor is needed even for cash transactions. For cash transactions, the payment processor doesn't need to be fully configured with a payment backend. It’s enough to just have a payment processor entry associated with the configuration record.
For more information about configuration records, go to Configure Fundraising and Engagement.
Error Messages
ISV error on record save (exception logged in the Web API)
A common error for any system that uses a disconnected architecture is a foreign key constraint violation. This error occurs when a related record isn't found in the Azure SQL database but does exist in Dynamics 365. From the available related records on the form that is presenting the error, make a change on the related record to trigger the update to Azure and correct the problem. If you're unsure about which foreign key exception is being thrown, use the logs form in the Web API in Azure, which will list the constraint.
ISV error on record save (no exception logged in the Web API)
When an ISV exception occurs and no corresponding exception is logged in the Web API, this error means Dynamics 365 can't get to the Web API at all. There are various reasons this error can occur. To resolve the issue:
- Ensure that the user experiencing the error has a configuration record set on their user record.
- Ensure that the database tables have been created using the migrations in the project.
- If the Web API URL is filled in the configuration record, remove it. For more information about the deprecation of Web API URL and API Padlock fields, go to Configuration record prerequisites.
Managed Package Deployment Considerations
When building the Fundraising and Engagement managed package using the solution packager, developers and database administrators might experience a series of warning messages displayed by the utility that look like:
Following root components are not defined in customizations:
Type=’SystemForm’, Id (or schema name)=’{00a8af62-bfa3-48b4-abc7-f81e7456fb1e}’,
Type=’SystemForm’, Id (or schema name)=’{01d7135d-ba58-433d-8f5e-6b681ad4d450}’,
These are known warnings, and you can continue. If you continue, the managed package should deploy as expected. This issue will be resolved in a future release.