AB-400 Explained: Synchronizing Dataverse with Change Tracking and Upsert

About this video

Learn how to synchronize Dataverse using Change Tracking and Upsert in this AB-400 Explained session. Explore a restartable synchronization pipeline with clear field ownership, stable record identities, incremental change retrieval, and durable checkpoints. Preserve destination-owned data while applying source updates and deletions. Topics covered: • Change readers, deterministic mapping, destination writers, and checkpoint storage • Source-owned replicated columns versus destination-owned operational fields • Composite Alternate Keys and Active index readiness • Incremental retrieval with RetrieveEntityChangesRequest and @odata.deltaLink • Paging cookies, DataToken capture, and durable token storage • UpsertRequest with KeyAttributes and mapped Attributes • Replaying row updates without creating duplicate logical records • Deletion tombstones and destination soft-delete policies • Committing checkpoints only after all destination changes succeed • Crash recovery and reconciliation after expired or invalid tokens For learners preparing for AB-400 and developers building reliable Dataverse synchronization integrations. #AB400 #Dataverse #PowerPlatform