What's changed: Created PL-400 Chapter 5, completing the textbook (domain: Develop integrations): publishing/consuming Dataverse events (IServiceEndpointNotificationService, webhook registration in the Plug-in Registration Tool, Azure Service Bus queues/topics, Azure Event Hub, choosing listening options) and data synchronization with Dataverse (change tracking delta retrieval, alternate keys, the UpsertRequest message).
5.2Data synchronization with Dataverse
Understand delta retrieval via change tracking, alternate keys, and synchronization with the UpsertRequest message.
Keeping an external system and Dataverse efficiently consistent requires delta retrieval and reliable matching.
5.2.1Change tracking
Enabling change tracking lets you efficiently retrieve only rows changed since the last sync (the delta). You no longer fetch everything each time, making large-data sync practical. Enable per table; the sync process keeps the prior token to fetch deltas.
5.2.2Alternate keys and UpsertRequest
External systems often don’t know Dataverse’s GUID primary key, so define alternate keys to uniquely identify a record by the external key (e.g., order number). For sync, use the UpsertRequest message to update if it exists, create if not in a single operation. This avoids "retrieve-then-branch," reducing conflicts and round-trips.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.