Edit

Troubleshoot dual-write issues in finance and operations apps

  • Article

This article provides troubleshooting information for dual-write integration between finance and operations apps and Dataverse. Specifically, it provides information that can help you fix issues with the Dual-write module in finance and operations apps.

Important

Some of the issues that this article addresses might require either the system admin role or Microsoft Microsoft Entra tenant admin credentials. The section for each issue explains whether a specific role or credentials are required.

You can't load the dual-write module in a finance and operations app

If you can't open the Dual-write page by selecting the Dual Write tile in the Data management workspace, the data integration service is probably down. Create a support ticket to request a restart of the data integration service.

Error when you try to create a new table map

Required credentials to fix the issue: The same user that setup dual-write.

You might receive the following error message when you try to configure a new table for dual-write. The only user that can create a map is the user who setup the dual-write connection.

Response status code does not indicate success: 401 (Unauthorized).

Error when you open the dual-write user interface

You might receive the following error message when you try to access dual-write from the Data management workspace:

login.microsoftonline.com refused to connect.

To fix the issue, sign in by using an InPrivate window in Microsoft Edge, an incognito window in Chromium, or an incognito window in Google Chrome. You must also unblock or clear third-party cookies.

Required role to fix the issue: System administrator in both finance and operations apps and Dataverse.

You might encounter the following error when linking or creating maps:

Response status code does not indicate success: 403 (tokenexchange).
Session ID: \<your session id\>
Root activity ID: \<your root activity\> id

This error can occur if you don't have sufficient permissions to link dual-write or create maps. This error can also occur if the Dataverse environment was reset without unlinking dual-write. Any user with system administrator role in both finance and operations apps and Dataverse can link the environments. Only the user who setup the dual-write connection can add new table maps. After setup, any user with system administrator role can monitor the status and edit the mappings.

Error when you stop the table mapping

You might receive the following error message when you try to stop the table mappings:

[Forbidden], [{"status":403,"source":"","message":"Error from token exchange: User is not allowed to access connection dynamicscrmonline/xxxxxx-xxxx-xxxx-xxxxxxxx"}], The remote server returned an error: (403) Forbidden.

This error occurs when the linked Dataverse environment isn't available.

To fix the issue, create a ticket for the Data Integration team. Attach the network trace so that the Data Integration team can mark the maps as Not running in the back end.

Enable parallel processing in finance and operations apps to improve performance

Enabling parallel processing can reduce the time needed to import data from Dynamics 365 customer engagement apps and Microsoft Dataverse to finance and operations apps.

To enable parallel processing in finance and operations apps, complete the following steps.

  1. Log in to your finance and operations environment.
  2. Go to Data management > Framework parameters.
  3. Select Entity settings and select Configure entity execution parameters.
  4. Add the parameters for parallel processing:
    • Import threshold record count – The number of records that must be met before parallel processing is enabled.
    • Import task count – The number of threads (tasks) to run in parallel.
  5. Select Save.

Errors while trying to start a table mapping

Unable to complete initial data sync

You might receive an error like the following when you try to run the initial data sync:

Unable to complete initial data sync. Error: dual-write failure - plugin registration failed: Unable to build dual-write lookup metadata. Error object reference not set to an instance of an object.

When you try to set that state of a mapping to Running, you might receive this error. The fix depends on the cause of the error:

  • If the mapping has dependent mappings, then make sure to enable the dependent mappings of this table mapping.
  • The mapping might be missing source or destination columns. If a column in the finance and operations app is missing, then follow the steps in the section Missing table columns issue on maps. If a column in Dataverse is missing, then click Refresh tables button on the mapping so that the columns are automatically populated back into the mapping.

Version mismatch error and upgrading dual-write solutions

You might receive the following error messages when you try to run the table mappings:

  • Customer groups (msdyn_customergroups) : Dual write failure - Dynamics 365 for Sales solution 'Dynamics365Company' has version mismatch. Version: '2.0.2.10' Required version: '2.0.133'
  • Dynamics 365 for Sales solution 'Dynamics365FinanceExtended' has version mismatch. Version: '1.0.0.0' Required version: '2.0.227'
  • Dynamics 365 for Sales solution 'Dynamics365FinanceAndOperationsCommon' has version mismatch. Version: '1.0.0.0' Required version: '2.0.133'
  • Dynamics 365 for Sales solution 'CurrencyExchangeRates' has version mismatch. Version: '1.0.0.0' Required version: '2.0.133'
  • Dynamics 365 for Sales solution 'Dynamics365SupplyChainExtended' has version mismatch. Version: '1.0.0.0' Required version: '2.0.227'

To fix the issues, update the dual-write solutions in Dataverse. Make sure to upgrade to latest solution that matches the required solution version.