Share
ReportWhen adding/deleting custom fields and publishing in CRM 365, the DES process doesn't send the schema change down to the target Azure DB. There are no failure notification shown for that entity. Is there a way to get DES to recognize it? Is there a manual way to just push the fields from DES?
This is the 2nd time I've done this since we went live with CRM 365 in October 2018. The 1st was adding a field, it had tons of failures but it took 24hrs for it to add the field to DES (not sure if Microsoft did something for us but we had to open a ticket for it). Now, the 2nd time, trying to delete a field, no failures shown, yet the field is still in target azure DB so DES hasn't removed it.
The problem is that DES worked in our lower environments both times on both scenarios, but when going to Production, DES doesn't work the same way.
We've never modified the table schema on the Azure DB side, but is that something we can do without breaking DES from still syncing? For example: Can we delete/add the custom fields in the dbo.contact table and update the Types (user-defined table types: ContactType)? Will manually touching the target DB break DES from syncing?
We need to know what our options are and steps on how to do this successfully and without having to open tickets with Microsoft.
Please advise. Thanks!
*This post is locked for comments
All responses (
Answers (
291,280
