Share
Report
45Hi everyone!
In my company we have created an export interface that uses an export project in data management. This project uses a custom data entity that joins some tables (12 tables in total to be precise, primary table is InventTable) and extracts only 20 fields from all the hundreds available from the joined tables.
As the above interface have to be incremental, we have enabled /all tables/ change tracking on the data entity, and set the export project to incremental push.
The problem we are having is that the change tracking triggers the export even if the 20 selected fields are not changed.
For example: my primary table is InventTable. Data entity read just ItemId, PmfProductType and a custom one from it. We expected to trigger the export if one of those fields change. Instead, if I change field /ItemType/, that's part of the table but not exported by DE, it exports the entire record again even if I am not interested in doing that.
For example: my primary table is InventTable. Data entity read just ItemId, PmfProductType and a custom one from it. We expected to trigger the export if one of those fields change. Instead, if I change field /ItemType/, that's part of the table but not exported by DE, it exports the entire record again even if I am not interested in doing that.
As we have activated the change tracking on all the tables of DE, this happens for every field of all 12 tables!
This obviously create a large amount of unnecessary exported items, and a heavy workload both for the export on our side and the import on the other side when the file is read.
Is there a way to use change tracking and trigger the export just for the fields selected by the data entity?
We have looked in Microsoft documentation, in visual studio and searched online, but with no success.
Nevertheless, this interface has been in production environment for almost two years and we never noticed this problem: has Microsoft changed something in data entities behaviour in the latest updates?
All responses (
Answers (
