Hi all
I configured a data entity for a BYOD Export to an Azure SQL database. I enabled the specific entity for ChangeTracking and it also shows me that "Track Deletes" is enabled.
However, whenever I delete a record from the mentioned entity, this is not reflected in the Azure SQL database. The record will still be available there.
Did i misunderstood something? I expected the record to be deleted in the Azure database as well?
Your help is really appreciated
Thanks
Andreas
This same behavior most likely happens for all entities which are based on ValidTimeState tables.
In general, if you query ValidTimeState tables in D365FO, you will get only the "active" records (ValidFrom <= today, ValidTo >= today). And this happens in the full push as well., just like you described.
But the data deletion in BYODB incremental push is based on actual deletes in the table (which the SQL change tracking notices). In this case there is no delete, so nothing is deleted from BYODB, either.
And it also means you can't use this feature to track address "deletes" (= disabling of address) with the out of the box capabilitites.
i guys
thanks for the fast answer
@Nikolaos:
If i run a "Full Push" the address will not be exported anymore (even if it is still available within the history view). So this tells me it should be deleted with the "incremental push".
Just tried it with the entity "Entities for a processing group" and you're right...with this one it seems to be working....which is already kind of progress if i compare to PU15
@Martin:
No, ValiTo field is still set to "2154-12-31 23:59:59.000" as for all the addresses.
If I go to D365 I can see the correct Expiration date on the deleted address within the history view...however, this date is not exported with the entity nor any other status information.....
So bottom line, this leaves me with the issue that i'm not able to track address deletes (same issue might appear for other entities).
kind regards
Andreas
The address record isn't deleted (otherwise you couldn't still see it in the history view", could you?); what has changed is the value of its ValidTo field.
Removing the address in D365FO doesn't actually delete the address from LogisticsPostalAddress table, so maybe it explains the behavior here. The address is just set as inactive (like you say, it can still be seen in the history view). If you try it with some simpler table / entity (not ValidTimeState controlled), are the deletes tracked correctly?
Hi Rahul
I can not confirm your answer.
Just tried it with Version 10 PU 24 and deletes are still not tracked as expected. Maybe I do have a wrong expectation, so I try to describe the whole process here:
- I create a new address for a custome - > address gets exported as expected within the entity "Party postal address V2"
- I remove the address in D365 (the address is now visible only within the "history view") -> when I run the BYOD Export Job, the address in they BYOD is not deleted or marked as deleted
Can you guys please correct me if my assumption is wrong that deletes like I described them above should be tracked?
kind regards and thanks
Andreas
with incremental push and 8.1 PU23 it is seen working.
With full push anyway covered.
Try with latest PU
So no other ideas?
Here my example with a little bit more details on the configuration:
Updates are loaded as expected on incremental basis into the Azure DB. However deletes in D365 are never really reflected in the Azure DB.
What's your experience with deletes and BYOD?
Regarding Version & PU:
your help is really appreciated
kind regards
What PU you are on ? Deletes are supported from PU 11 onwards.
#1
André Arnaud de Cal...
294,141
Super User 2025 Season 1
#2
Martin Dráb
232,881
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
