Views:

Applies to Product - Dynamics 365 Commerce
 

What’s happening?
          Data from the F&O system is not being synchronized with Dataverse (CE), or vice versa, due to errors encountered during the Dual-Write process.
 

Reason:
          Dual-write initial and live sync may not be working as expected
 

Resolution:    
            Run the Dual-Write Health Check:

  1. In the finance and operations apps environment, navigate to the dual-write page.
  2. On the Action Pane, select the health check option.
  3. Follow the steps in the dual-write health check wizard.

    Prerequisite Check:
  4. Ensure that system requirements and prerequisites are met.
  5. Verify that required solutions are installed and permissions are configured.

    Dependency Validation:
  6. Ensure that the finance and operations apps environment and Dataverse environment are linked.
  7. Configure the dual-write entity maps to sync between the linked environments.
  8. Fix any errors in the prerequisite health check before performing dependency validation.

    Possible Errors and mitigation steps:
  9. If there are missing Dataverse API Hub connections, reset the dual-write connections.
  10. If there are missing finance and operations apps API Hub connections, reset the dual-write connections.
  11. Address any company mismatches between dual-write and Dataverse by removing mismatched companies or resetting dual-write connections.
  12. Clean up stale dual-write configurations in both Dataverse and finance and operations apps.
  13. If there is a default team name mismatch, reset the dual-write connection or update the connection details with support.
  14. Update the owning team directly on the company record in the Power Apps maker portal if the default owning team is not present.

    Check Activity Log:
  15. Review the activity log for related errors and share the activity ID or correlation ID for further investigation.
For more detailed troubleshooting steps, refer to the dual-write troubleshooting guide.