Replication package error

  • 38Views
  • Last Post 3 weeks ago
0
votes
Robert Brodskiy posted this 3 weeks ago

Hi,

I'm doing replication from Dynamics 365 to Azure SQL Database. This replication is running on the scheduled bases. But the strange thing happened after microsoft add more columns to the replicated entity. I'm getting an error saying table on SQL side is missing those added columns.

So, why SKYVIA desides to replicate added columns instead of keep them unchecked (not replicating). Buy the way, I did a test and add some custom columns to the replicated entity and SKYVIA did what it should do, just kept them unchecked.

Regards,

Order By: Standard | Newest | Votes
-1
votes
Serhii Muzyka posted this 3 weeks ago

Hi Robert,   

Thank you for contacting Skyvia Support.   

 

In case you haven't done any changes to your replication task or metadata, the error shouldn't happen.   

Possible that those fields changed their names and that's why the package started failing. If a replicated field or a replicated object is deleted or renamed in the data source, the replication package will start failing until you perform the necessary changes to it.     

Please try to run the full replication again, resetting LastSyncTime with Drop and Create table options enabled, and let us know if this situation repeats in the future.     

 

Best regards, 

Serhii        

0
votes
Robert Brodskiy posted this 3 weeks ago

Hi Serhii,

Thanks for the response to my question.

 

Unfortunatly, fields mentioned above has not been changed or removed from destination table. Microsoft adds them to the source table. And that's where the problem begins.

0
votes
Serhii Muzyka posted this 3 weeks ago

Hi,

We are really sorry for the inconvenience.

 

We investigated this situation deeper and found out the cause.

When the object is selected in the replication package, all the fields of this object are automatically selected. Then, if the new fields are added to the source and the metadata cache is updated on our side(to math the API), these fields will automatically be added to the replication task and because they are not in the target, there will be an error.
In order for the fields to not be automatically selected, you need to click 'edit' for the required task in the package and remove any field. This equates that the fields are selected individually, and not all (select *). You can see different markings on the screenshots below:

We hope this clarifies the situation. 

 

Should you have any other questions, don't hesitate to reach out.

 

Best regards,

Serhii

New Ticket
Categories
Popular Tags
Close