Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Tim Stutzman]

Hello,

We are currently using BYOD to export from D365 to Azure SQL server.  We have been live a little over 3 months, therefore I am still learning about the BYOD functionality.  

My question is that I am noticing several (not all) data entities we are exporting do not replicate correctly to Azure.  For example, one of the data entities we are exporting is the CDS Sales Order Lines data entity.  When a sales order line gets deleted in D365, the line does not get removed in Azure.  I have to un-publish the CDS Sales Order line data entity and re-publish then export again and it will be removed.  I have the export job set to incremental.  

On the other hand the Sales Order Lines V2 data entity if a sales order line gets deleted in D365, it is replicated to Azure correctly and the sales order line will no longer be in Azure after the BYOD export.  This export job is set to incremental too.  

I have done through testing and it seems it is certain data entries that I am exporting that have this behavior.  I believe I am setting all the data entities to export in data management the same, but wanted to reach out and see if maybe I am setting something up incorrectly, if anyone else has seen this behavior or do I need to create an MSFT support ticket.

Any help is appreciated.

Thanks,
Tim

——————————
Tim Stutzman
Pure Archery Group
Eugene OR
——————————

[Nagasatya Devarakonda]

Hi,

Quick question, for the entities that have the issues with incremental loads, do you have change tracking enabled on these entities before publishing them to BYOD?

Regards,

——————————
Nagasatya Devarakonda
Business Intelligence Architect
Liquor Stores Limited Partnership
Edmonto AB
——————————
——————————————-

[Tim Stutzman]

Hi Nagasatya,

I do have the change tracking enabled, but I most likely enabled after publishing if I remember correctly.  Sounds like I should enable change tracking then publish.  Is there a way to rectify?

Thanks,
Tim

——————————
Tim Stutzman
ERP Systems Manager
Pure Archery Group
Eugene OR
——————————
——————————————-

[Nagasatya Devarakonda]

Hi Tim,

Yes, that is correct. It is usually the following order.
1. If there are any mapping changes on the entities, regenerate mapping on the entity.
2. If an entity is already on an export job, remove it from the job.
3. If an entity is already published, drop the entity.
4. Enable change tracking. 
5. Publish entity.
6. Add it to an export job with incremental push.

From my experience of almost 3 years with BYOD, these steps mostly work. 

Hopefully this resolves your issue.

Regards,

——————————
Nagasatya Devarakonda
Business Intelligence Architect
Liquor Stores Limited Partnership
Edmonto AB
——————————
——————————————-

[Tim Stutzman]

Hi Nagastya,

Regarding #1 when you say regenerate the mapping on the entity, how do you go about doing that task?

Thanks,
Tim?

——————————
Tim Stutzman
ERP Systems Manager
Pure Archery Group
Eugene OR
——————————
——————————————-

[Nagasatya Devarakonda]

Hi Tim,

Under Data Management => Data Entities => Select Data Entity => Click on Modify Target Mapping => Generate Mapping => Click Yes on pop up window => Save.

Hopefully this helps.

Regards.

——————————
Nagasatya Devarakonda
Manager, Data & Analytics
Alcanna
Edmonton AB
——————————
——————————————-

[Tim Stutzman]

Hi Nagasatya,

This helps a lot.  Thank you for your assistance!

Tim

——————————
Tim Stutzman
ERP Systems Manager
Pure Archery Group
Eugene OR
——————————
——————————————-

[Nagasatya Devarakonda]

I am glad it helped. 
Cheers

——————————
Nagasatya Devarakonda
Manager, Data & Analytics
Alcanna
Edmonton AB
——————————
——————————————-