Share via

Help us help you with technical issues for Finance and Supply Chain Management

  • Article

Some basic troubleshooting can help you resolve a problem before you have to open a support ticket. This article provides guidance, tips, and resources for troubleshooting your Finance and Supply Chain Management solutions. If your issue isn't covered, be sure to collect all the information you can before you submit a ticket. Learn more in Help us help you - general questions for Power Platform and Dynamics 365.

Technical troubleshooting

A key tool for diagnosing technical and functional issues with Dynamics 365 Finance and Supply Chain Management is the platform's monitoring and telemetry capabilities in Azure Application Insights. Learn more at Monitoring and Telemetry using Microsoft Dynamics 365 Finance and Microsoft Dynamics 365 Supply Chain Management.

Performance

This section discusses best practices and tools to help you optimize the performance and stability of your Finance and Supply Chain Management solutions. Learn more in the following articles:

Best practices

Keep your solution and environments up to date with hotfixes and platform and quality updates.

Regularly log and review performance risks so that you can address potential bottlenecks.

Use the Dynamics 365 migration framework instead of OData for large data transfers, and use set-based data entities and parallel processing to speed up data movement. Build custom data entities to eliminate unnecessary columns and tables. Learn more in the following articles:

Set up batch processing with priorities and threads. Learn more in Priority-based batch scheduling.

Use the Optimization advisor workspace to identify and improve inefficient business processes. Learn more in Optimization advisor overview.

Use noncontinuous number sequences with preallocation to prevent locking issues. Learn more in Performance considerations for number sequences.

Run data cleanup routines regularly to free up system resources. Learn more in Cleanup routines in Dynamics 365 Finance and Dynamics 365 Supply Chain Management.

When you develop and customize your solutions, minimize the use of nested loops and round-trips to the SQL database. Develop cohesive, multithreaded batch jobs to enable processing across multiple servers. Optimize data handling by avoiding record-by-record operations. Instead, use bulk processing methods such as insert_recordset and update_recordset.

Consider your security settings. Admin roles typically perform better than restricted users.

Performance tools

Data integrations and management

Check the list of common errors, error codes, and known limitations on managing data in Data management error descriptions and known limitations.

In some cases, cleaning up the entity history can resolve issues. Learn more in the following articles:

Throttling can be a factor in integration performance issues. Learn more in Throttling prioritization.

API service protection limits can affect high-volume integrations. Learn more in Service protection API limits.

If you still need to open a support ticket after you review the suggestions in this section, provide the following information.

For issues with oData:

  • Does the issue occur with a single entity or with multiple entities? With a standard entity or a customized entity?

  • What's the syntax of the OData call that's being made?

  • Can you reproduce the issue by taking the same action in the Excel add-in or another tool? Learn more in Configure and use the Excel add-in for business performance planning.

  • Is the OData endpoint available for this environment? To check, browse to the equivalent of the following URL: <Your organization's root URL>/data/data/$metadata

For issues with Web services:

  • What's the name of the web service, and which model is the service part of?

  • Is the issue related to a non-Microsoft module?

For issues with logic apps or flows:

  • Which connectors does your logic app or flow use?

  • Include a screenshot of the logic app or flow and the steps it includes.

  • Are any of the steps failing explicitly?

  • What error do you get?

For issues with DIXF/DMF APIs:

  • Are you using Data import/export framework (DIXF) APIs, Data management framework (DMF) package APIs, or recurring integration APIs?

  • Is the problem with export or import of data?

  • If you use DIXF APIs, share the execution ID of the DIXF import or export that's experiencing the problem.

  • Does the issue occur with a single entity or with multiple entities? With a standard entity or a customized entity?

  • In your app, go to Data Management > Framework parameters and select the Compatibility options tab. Include in your ticket the values of the fields in the Data project and job compatibility and Recurring integrations compatibility tabs. Learn more in Data import/export framework parameters.

Fabric, Synapse, Dataverse, and dual-write

Review the following troubleshooting guides:

If you still need to open a support ticket after you review the suggestions in this section, provide the following information:

  • Is the issue related to a profile configuration or data synchronization or missing or duplicate values?

  • Which scenario are you using to set up the link: Link to Synapse workspace, CSV incremental, or Link to Fabric?

  • Provide any correlation IDs.

  • What's the affected Azure Synapse Link profile name?

  • What's the related table or data entity?

Alerts

Learn more in Alerts overview.

Make sure that the alert rule is set up and that the user to notify is specified.

Check if Trigger is created on the Alert rule table. If not, delete the alert rule and recreate it.

Delete all the rules that belong to the same table.

Rule IDs can be checked in the EventRule table that has duplicate Rules on same table.

After deleting the rules, check for the orphan triggers for alerts and database logging. If any we have to delete the orphan triggers.

Truncate the EventCUD/EventCUDLines tables if the records volume is huge. Learn more in Notification clean up | System administration.

Make sure that only one batch job runs at a time for change tracking. More than one can cause deadlocks, a situation in which two processes are each waiting for the other one to finish.

Check whether the alert rules are created on system tables or DMF tables. We recommend that you never create alert rules on these tables. Tables with names that start with SYS are system tables. DMF tables are used for data management.

For email alerts, verify the email configuration in Dynamics 365 or at the email server end, including the alert rule name and details like the table name and the triggering events.

If you still need to open a support ticket after you review the suggestions in this section, provide the following information:

  • What are the symptoms on the alert?

  • What's the name and configuration of the alert?

Document management

Make sure that you configured document management correctly. Learn more in Configure document management.

If the issue is related to SharePoint storage, follow the troubleshooting steps in Troubleshooting SharePoint communication.

If you still need to open a support ticket after you confirm the configuration, provide the following information:

  • Is the issue with Azure Blob Storage or SharePoint?

Document routing agent

Review the following articles:

On-premises deployments

If you deploy Dynamics 365 apps on-premises, the support team at Microsoft has virtually no visibility into your environment setup. We recommend that you follow the suggestions in Troubleshoot on-premises deployments.

If you need to open a support ticket, make sure you capture diagnostics. Learn more in On-premises diagnostics.

Migration from Dynamics AX 2012 to Dynamics 365

An upgrade from Dynamics AX 2012 to Dynamics 365 is a complex operation with many moving parts. The upgrade can be split into two areas, upgrading the code and upgrading the data. The data upgrade can be performed in a development environment or in a Tier 2 or higher sandbox environment. Review the following troubleshooting guides:

If you encounter performance issues during the upgrade, review the following articles:

If you need to open a support ticket, include the type of upgrade process you're having an issue with. The replication and data upgrade involve many steps. Review the following articles to determine the specific step where the issue is occurring.

Leave us feedback

Is there anything else you need help with? Leave us feedback.