We are using the common data model to feed other system with the "When a record is updated"-trigger in Logic Apps. We are getting data into the CDS with the prospect to cash scenario (synchronise data between D365fO and the CDS). So far so good.
My expectation is:
When I change in D365fO one record, after synchronisation CDS mark it as modified
When I dont change records in D365fO, after synchronisation CDS information aren't updated (not modified)
What really happens:
Everytime I start the sync all CDS records will be mark as modified, but I haven't changed them.
This leads me to the question..
..do I misunderstand the common data model/service?
I agree with you that the CDS can only "export" data via flows, thats clear so far.
The foreign/third party system would e.g. generate a new record directly on D365fO (via OData), so next sync would push the data into CDS.
But my message was about the export trigger "When a record is updated" itself, which mark existing record in the CDS as modified when the synchronisation is running. But I don't change any record on D365fO side.
My setup: 01Task
02Connection 03Execution1of2 03Execution2of2
What I additonally can say the modified timespamp in the data view of the vendor entity, was set to the time of sync. That implements that the trigger would run for each record although no one record was modified in D365fO. So I would give you some overviews of the logic app and the execution but this stupid project killed my whole MSDN credit for Azure.
If you need a more detailed description let me know.
I got a response of the PRINCIPAL PROGRAM MANAGER of Microsoft in another forum: "Prospect to Cash uses bulk APIs to upload data. So, it avoids the trigger logic by default. We can enable this but have not currently done so."