Feedback Edit

Reset Dataverse synchronization

  • Article
  • 2 minutes to read

Important

The functionality noted in this article is currently available for customers on the stand-alone Dynamics 365 Human Resources. Some or all of the functionality will be available as part of a future release on the Finance infrastructure after Finance release 10.0.25.

Applies to these Dynamics 365 apps:
Human Resources

Issue

Records are not synchronized between Microsoft Dynamics 365 Human Resources and the entities in the Human capital management (HCM) Common solution in Microsoft Dataverse. For more information about synchronization, go to Configure Dataverse integration. Failure to synchronize correctly can occur when the Dataverse integration retry or Dataverse integration missed request sync batch jobs are stuck in an Executing state.

Resolution

When the Dataverse Integration retry or Dataverse integration missed request sync batch jobs are stuck in an Executing or Canceling state, you can reset the status. This can be done by cancelling the batch job by following the guidance in Reset stuck batch jobs. After you cancel the batch job, you can reset the batch job by setting it to a Waiting status. The batch job will then run during the next scheduled run time.

  1. If you haven't done so already, enable the Enhanced batch abort feature in Feature management.

    1. Go to the Feature management page (System administration > Summary > Feature management).
    2. Select the All tab.
    3. Select the Feature name column and filter by Enhanced batch abort.
    4. Select the Enable action if it is not already enabled.

  2. Turn off the Dataverse integration.

    1. Go to the Microsoft Dataverse integration page (System administration go to Links > Integrations > Dataverse configuration).
    2. Set Enable Dataverse integration to No.

  3. Cancel the Dataverse integration retry batch job.

    1. Go to the Batch jobs page (System administration go to Links > Batch jobs > Batch jobs).
    2. Filter the Job description column by Integration.
    3. Select the Dataverse integration retry batch job.
    4. On the action ribbon, select Batch Job, Force cancel, and then select Yes to confirm.

    Note

    Depending on when the integration was first enabled, the batch job may have the description Common Data Service integration retry. Select this batch job if it is listed, instead of the Dataverse integration retry batch job.

  4. Delete all Dataverse integration batch jobs.

    1. On the Batch jobs page, select the Dataverse integration missed request sync, Dataverse integration retry, and Dataverse integration initial sync batch jobs.
    2. On the action ribbon, select the Change status action.
    3. Select Withhold, and select OK.
    4. On the action ribbon, select the Delete action, and then select Yes to confirm the action.

  5. Turn on the Dataverse integration batch jobs.

    1. Go to the Microsoft Dataverse integration page (System administration > Links > Integration > Dataverse configuration).
    2. Set Enable Dataverse integration to Yes.

  6. Go to the Batch jobs page and confirm that the Dataverse integration retry and Dataverse integration missed request sync batch jobs have been created.

With the batch jobs recreated, you can now monitor the Dataverse integration retry batch job to see how long the job takes to execute. You can then verify that the records are synchronizing correctly to the HCM Common solution in Microsoft Dataverse.

See also

Configure Dataverse integration
Reset stuck batch jobs

Help us understand

We want to learn more about how people use Microsoft's custom Help toolkit. Take the survey (in English) and help us understand: https://forms.office.com/r/A4cUJgjkD1.