Troubleshooting guide for data integration

Enable plug-in trace logs in Common Data Service and inspect the dual-write plug-in error details


Dynamics 365 for Finance and Operations is now being licensed as Dynamics 365 Finance and Dynamics 365 Supply Chain Management. For more information about these licensing changes, see Dynamics 365 Licensing Update.

If you experience an issue or error during dual-write synchronization, follow these steps to inspect the errors in the trace log.

  1. Before you can inspect the errors, you must enable plug-in trace logs. For instructions, see the "View trace logs" section of Tutorial: Write and register a plug-in.

    You can now inspect the errors.

  2. Sign in to Microsoft Dynamics 365 Sales.

  3. Select the Settings button (the gear symbol), and then select Advanced Settings.

  4. On the Settings menu, select Customization > Plug-In Trace Log.

  5. Select Microsoft.Dynamics.Integrator.CrmPlugins.Plugin as the type name to show the error details.

Inspect dual-write synchronization errors

Follow these steps to inspect errors during testing.

  1. Sign in to Microsoft Dynamics Lifecycle Services (LCS).
  2. Open the LCS project to do dual-write testing for.
  3. Select Cloud-hosted environments.
  4. Make a Remote desktop connection to the application virtual machine (VM) by using local account that is shown in LCS.
  5. Open Event Viewer.
  6. Go to Applications and Services Logs > Microsoft > Dynamics > AX-DualWriteSync > Operational. The errors and details are shown.

Follow these steps to update links.

  1. Go to the application environment.

  2. Open Data Management.

  3. Select Link to CDS for apps.

  4. Select all the mappings that are running, and then select Stop.

  5. Select all the mappings, and then select Delete.


    The Delete option isn't available if the CustomerV3-Account template is selected. Clear the selection of this template as required. CustomerV3-Account is an older provisioned template and works with the Prospect to Cash solution. Because it's globally released, it appears under all templates.

  6. Select Unlink environment.

  7. Select Yes to confirm the operation.

  8. To link the new environment, follow the steps in the installation guide.