Dynamics Community Forum Thread Details

SyncError Dependency Issue

Since we installed the December 2016 update (8.2.0000.0749) in our development and test environment we are having issues. We are preparing an upgrade from CRM4 to CRM 365. Issues arise when the organization database has been imported to CRM 365. First a managed solution was applied to change all customization to managed.

After importing a new solution version it is not possible to apply the upgrade anymore (it was before the December update).The new solution version would delete custom entities from the system that have been in the organization prior to the upgrade. (initially all cutomizations were unmanaged. We applied a managed solution to change all customization to managed. We now want to install and apply a solution upgrade that will remove redundant entities from the system.) When we apply the upgrade we get the following error:

The list of details displayed when clicking on Details is empty.

A very similar issue, which is assumed to have the same cause

Technically the same issue arises in a development organization that is upgraded to CRM 365 after applying the December 2016 upgrade, i.e. by importing the organization's CRM 2015 database into a new organization in dynamics CRM 365 using the deployment manager. Deleting one of the custom entities after the upgrade fails. Error message:

In this case error details are not empty:

This is a CRM issue, since the relationship to the Sync Error entity should not be blocking the deletion of a custom entity. It is a relationship that is implicitly added to any custom entity.

Impact

If I only were removing a single entity at one point of the migration process, it would be possible to delete the 1-n relationship of the custom entity to the Sync Error entity, but due to a whole list of necessary deletions during the migration of our large database this is not an option.

We need another solution to resolve this issue.

Database Script?

By comparing an upgraded database that was upgraded before the December 2016 upgrade was installed to a database that was upgraded after the upgrade was installed, I have come up with a script that deletes entries in the DependencyBase and DependencyNodeBase tables. This is definitely not a supported route for the migration process. Since this will be performed on a customer's production database, we think it is necessary to have a supported solution from Microsoft for this issue.

Quick Links

Leaderboard