1
Delete operations should be supported when doing incremental push of custom entities.
For example:
Currently we have a few custom entities that are cross company, one of the is an entity for LedgerJournalTable and the entity primary Key is the combination of JournalNum and DataAreaId.
When a record is created, or updated it works as expected however when a journal is deleted, it will delete it in the BYOD across all companies.
When doing an incremental push after an update, the push only updates the Journal that was updated in D365 even if the Journal number exists in other companies it updates the correct company in BYODB. Based on that, it seems that the system can identify the records in the various companies, but it is just currently not supported for Delete, because it will delete across all companies in BYODB.
For example:
Currently we have a few custom entities that are cross company, one of the is an entity for LedgerJournalTable and the entity primary Key is the combination of JournalNum and DataAreaId.
When a record is created, or updated it works as expected however when a journal is deleted, it will delete it in the BYOD across all companies.
When doing an incremental push after an update, the push only updates the Journal that was updated in D365 even if the Journal number exists in other companies it updates the correct company in BYODB. Based on that, it seems that the system can identify the records in the various companies, but it is just currently not supported for Delete, because it will delete across all companies in BYODB.
STATUS DETAILS
Declined
Administrator on 5/8/2020 3:31:27 PM
It is not clear from the description as to what is the feature ask. Can you pls drop me an email at sunilg@microsoft.com to discuss this scenario further? We want to make sure we dont lose this use case due to misunderstanding on our part. Thanks.