Microsoft Dynamics 365 | Integration, Dataverse...

Data Export Service - New column not added to destination table

(0) Share

Report

Posted on by Community Member Microsoft Employee

Hi all,

I noticed that the DES sync had several failed records. Turns out that a new added column in CRM was missing in the destination table. From what I understand, new columns shall automatically be added to the destination table. This has apparently failed in my environment.

My question is, can I just add this column to the destination table and DES will sync this column? Are there any other considerations that I should take into account?

Thanks!

All responses (6)

Answers (0)

Community Member Microsoft Employee on at

Like (0)

Report

RE: Data Export Service - New column not added to destination table

Thank you Wahaj.

The table has several million rows. I need to figure out the correct way to approach this, without losing any data.
Suggested answer

Wahaj Rashid 11,319 on at

Like (0)

Report

RE: Data Export Service - New column not added to destination table

Hi,

If data is no huge you can try re-adding the table.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Data Export Service - New column not added to destination table

Hi,

digging into this a bit more I have found the following:

The column has been added to the AttributeMetaData table in the destination. And, looking in the log for the azure sql db, the query

ALTER TABLE [dbo].[contact] ADD [my_field] [bit] NULL did run but apparently, the transaction was not commited, probably because of performance issues on the database. Note, the query was created and run automaticaly by DES, not by me.

Ok, so your suggestion would be to delete the table and re-create the export profile?

Thank you for your swifts replies.
Suggested answer

Wahaj Rashid 11,319 on at

Like (0)

Report

RE: Data Export Service - New column not added to destination table

Hi,

I would not suggest the last option (to alter db manually).

When was the field added? How many time resync happened? Did you try to resync failed records?

Please look into following docs to troubleshoot:

https://docs.microsoft.com/en-us/power-platform/admin/replicate-data-microsoft-azure-sql-database#resolving-synchronization-issues

Because it is a Production environment, re-configuring Export Profile is not an ideal solution, unless target entity records are less. Please note, only deslecting won't help, you have to drop the table in DB too:

https://docs.microsoft.com/en-us/power-platform/admin/replicate-data-microsoft-azure-sql-database#drop_entity

Please also verify that Change Tracking is enabled on the entity:

https://docs.microsoft.com/en-us/power-platform/admin/enable-change-tracking-control-data-synchronization

If still it isn't resolved, I would suggest to open a ticket with Microsoft.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Data Export Service - New column not added to destination table

Thank you for your answer, Wahaj.

This is a production environemt so I guess your suggestion would be to update the Export Profile. What would be the best approach? Deselecting my entity in the profile and click Update, then let it sync and the after that selecting my entity again and click Update? What will happen with my destination table when I deselect and then select it in my Export Profile?

Googled some more and found this: code2life.blogspot.com/.../how-to-create-new-missing-columns-for.html
But you would not recomend this, correct?

Thanks.
Suggested answer

Wahaj Rashid 11,319 on at

Like (0)

Report

RE: Data Export Service - New column not added to destination table

Hi,

Thank you for your query.

Is this sandbox environment? If yes, please look at the answer on following thread:

https://community.dynamics.com/365/f/dynamics-365-general-forum/381954/data-export-service-does-not-re-sync

Won't suggest to create the field manually in the table, try updating (or recreating the Export Profile):

https://docs.microsoft.com/en-us/power-platform/admin/replicate-data-microsoft-azure-sql-database#modify-an-existing-export-profile