You’re offline. This is a read only version of the page.
65
Hi Tracy,
thank you for your answer. I read the article and it's ok for me. I have only a problem... i don't know the correct procedure to republish a dataentity in Byod... I mean...
I Have a dataentity with change tracker enabled and in Byod is ok... I make an update (for example I add a new field in DE) ... the steps that i do are:
1) remove the dataentity from the batch job
2) disable the change tracker on the dataentity
3) drop entity (this step remove the staging table in the Byod)
4) publish the dataentity (the staging table is create in the byod)
5) enable the change tracker in the dataentity
6) add the dataentity in the batch job with incrememtal push
the problem is that now the batch export only the record update after enable the change tracker and not run the full push to recreate all the record in the destination (like the first time)... I don't know how to recreate the byod align to d365 (all record in the staging). I think it is necessary a manual full push before to re-set an incremental push...is my think correct?.... is there a article about this issue?
Thank you
Ciao
Michele
Please refer to docs.microsoft.com/.../export-entities-to-your-own-database, for incremental push, whenever a new record is inserted, or a record is added or deleted, the corresponding change will be reflected in the destination entity. We recommend that you first enable change tracking and schedule a export job with incremental push. This will take care of the first full push and the subsequent incremental exports.
HI Michele,
The incremental approach is recommended and faster compared to a full table export. If you go for the incremental option, there will be a SQL trigger activated. This knows exactly which records were changed or added.
Hi Andrè,
not all entities...but the most important (we have create custom dataentites based on the standard table of d365 with the only necessary data) in order to create reporting purposes. Now we export purch data, sales data, inventdim and inventtrans (and other linked to these).... but the issue is understand if the incremental export is better than full export when the data will increase (and if the change tracking performance set in the inventtrans entity can reduce the performance of d365)... or if the time to check the difference between D365 and Byodb is better than truncate the staging table before D365 do full export.
thank you for your feedback
Ciao
Michele
Hi Michele,
Do you really need to export all entities? For what reason? The cost for Azure SQL might become too high. I would focus on only the data which is required to have in a BYOD for e.g. reporting purposes.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (