Study guide
9.3 Data Synchronization with Change Tracking & Alternate Keys
Microsoft Power Platform Developer Associate PL-400
Track your progress as you read
Finished sections get a check mark.
1 Introduction, Exam Overview & Developer Toolchain
0.1 PL-400 Exam Facts 0.2 Audience Profile & Required Developer Skills 0.3 The Power Platform Developer Toolchain 0.4 Extension-Point Map & AI in the Developer Workflow
2 Create a Technical Design
1.1 Analyzing Technical Architecture and Choosing Out-of-the-Box vs. Custom Solutions 1.2 Designing Authentication, Authorization, and Security Architecture 1.3 Deciding Where Business Logic Runs and Choosing the Right Table Type 1.4 Designing Reusable Power Apps Components and Custom Connectors 1.5 Designing Dataverse Code Components, Automations, and Integrations
3 Build Power Platform Solutions
2.1 Managing Power Platform Environments for Development 2.2 Dataverse Security Roles for Code Components, Least Privilege & Troubleshooting Operational Security 2.3 Solutions, Managing Dependencies & Solution Layers 2.4 Environment Variables & Connection References 2.5 Power Platform Pipelines & CI/CD with Power Platform Build Tools
4 Implement Power Apps Improvements
3.1 Complex Power Fx Formulas and Functions 3.2 Building Reusable Canvas Component Libraries 3.3 Invoking Power Automate Cloud Flows from a Canvas App 3.4 Troubleshooting Canvas and Model-Driven Apps with Monitor and Browser Debugging Tools 3.5 Optimizing Canvas and Model-Driven App Performance
5 Extend the User Experience
4.1 The Client API Object Model & JavaScript Form Scripting 4.2 Event Handler Registration & Navigation to Custom Pages via the Client API 4.3 Client Scripting Against the Dataverse Web API; Command Bar & Buttons with Power Fx and JavaScript 4.4 PCF Fundamentals: The Component Manifest & Lifecycle Events 4.5 Implementing PCF Component Interfaces; Device, Utility & Web API Features 4.6 Packaging, Deploying & Consuming a PCF Component
6 Extend the Platform: Dataverse Plug-ins & Custom APIs
5.1 Plug-in Fundamentals & the Event Execution Pipeline Stages 5.2 Execution Context & Implementing Business Logic in Plug-ins 5.3 Pre/Post Images & Organization Service Operations in Plug-ins 5.4 Registering Plug-ins with the Plug-in Registration Tool & Optimizing Plug-in Performance 5.5 Custom API Messages & Plug-ins That Implement a Custom API 5.6 Configuring Dataverse Business Events
7 Extend the Platform: Custom Connectors
6.1 Open API Definitions: Building and Extending a Custom Connector 6.2 Authentication and Policy Templates for Custom Connectors 6.3 Importing Definitions and Creating Connectors for Azure Services 6.4 Azure Functions in Custom Connectors and Data Transformation
8 Extend the Platform: Platform APIs & Azure Functions
7.1 Dataverse Web API Operations & OAuth Authentication 7.2 Organization Service Operations, Concurrency, Transactions & Bulk Operations 7.3 Service Protection API Limits & Retry Policies 7.4 Azure Functions for Long-Running, Scheduled & Event-Driven Workloads 7.5 Authenticating to Power Platform with Managed Identities
9 Extend the Platform: Power Automate Cloud Flows
8.1 Dataverse connector triggers/actions, trigger filters & retry policies 8.2 Complex expressions & flow control with error handling 8.3 Sensitive input/output parameters & Azure Key Vault 8.4 Reusable child flows & Microsoft Entra ID service principals
10 Develop Integrations
9.1 Publishing Dataverse Events: IServiceEndpointNotificationService & the Plug-in Registration Tool 9.2 Registering Service Endpoints: Webhooks, Azure Service Bus & Event Hub 9.3 Data Synchronization with Change Tracking & Alternate Keys 9.4 Upsert-Based Synchronization with the UpsertRequest Message
11 Exam Readiness & Practice
10.1 Cross-Domain "Where Do I Implement This?" Decision Framework 10.2 Exam-Day Strategy, PL-400 Item Styles & Study Plan
9.3 Data Synchronization with Change Tracking & Alternate Keys
Key Takeaways Explain This Topic AI
Change tracking lets an external system retrieve only the records created, updated, or deleted since its last sync, using a token instead of re-pulling the entire table every time.
Change tracking is enabled per table through the 'Track changes' advanced option (or EntityMetadata.ChangeTrackingEnabled) and, once enabled, cannot be disabled.
The Web API returns change data through the Prefer: odata.track-changes header and an @odata.deltaLink containing the token for the next request; the SDK uses RetrieveEntityChangesRequest and a DataToken.
Unprocessed change tokens expire after a default of seven days (ExpireChangeTrackingInDays), after which a client must perform a full resync.
Alternate keys let up to 16 columns from an external system's own identifier uniquely identify a Dataverse row, avoiding the need to store or look up the platform-generated GUID.
Last updated: July 2026
Publishing individual events in near real time, as covered in the previous two sections, isn't the only integration shape PL-400 tests. Many integrations are batch or periodic — an external ERP, data warehouse, or mobile app periodically asks Dataverse "what's changed since I last asked?" That pattern depends on two developer features: change tracking , which answers the "what changed" question efficiently, and alternate keys , which let the external system identify Dataverse records using its own identifiers instead of the platform's GUIDs.
Change Tracking: Syncing Only What Changed
Without change tracking, a synchronization job has to pull the entire table every time and compare it against its own copy to work out what's new — expensive and slow as tables grow. Change tracking solves this by having Dataverse hand back a token representing a point in time; on the next request, the client passes that token back and receives only the records that changed since then.
Enabling it: Change tracking is a per-table property. In the maker portal, open the table's Advanced options and turn on Track changes ; programmatically, set EntityMetadata.ChangeTrackingEnabled to true . Not every table is eligible — check EntityMetadata.CanChangeTrackingBeEnabled before trying. Once enabled for a table, it cannot be disabled , which is worth remembering before flipping it on for a table with heavy write volume purely for a one-off integration.
Using it via the Web API: send a GET request with a Prefer: odata.track-changes header. The response includes an @odata.deltaLink — a URL containing an opaque $deltatoken — that you store and use as the URL for your next request instead of the original query. That follow-up response contains only new/updated rows plus deleted rows flagged with "reason": "deleted" . Standard query options like $filter , $orderby , $expand , and $top are not supported on a tracked-changes request.
Using it via the SDK: the RetrieveEntityChangesRequest message returns a RetrieveEntityChangesResponse whose EntityChanges property carries a DataToken (save it for the next call), a collection of NewOrUpdatedItem / RemovedOrDeletedItem entries, and MoreRecords / PagingCookie for paging through large result sets. The very first call — made with no token — returns every existing record as "new," which is how you perform the initial full load before switching to incremental sync.
Constraints to know:
Only one table can be tracked per RetrieveEntityChanges call.
Unprocessed change data expires after a default of seven days , controlled by the organization's ExpireChangeTrackingInDays setting — wait longer than that between syncs and the token is no longer valid, forcing a full resync.
New/updated records are returned before deleted records, and large result sets page at 5,000 records per page.
Alternate Keys: Identifying Records Without the GUID
An external system almost never knows a Dataverse record's primary-key GUID — it knows its own identifier (a legacy ERP customer number, a product SKU, a partner system's ID). An alternate key lets you designate one or more columns on a table as a secondary unique identifier that Dataverse enforces with a database index, so external callers can address a record by that business key instead.
Key facts for the exam:
- Constraint Value
- Max columns per alternate key 16 (also capped at 900 bytes total, a SQL index limit)
- Max alternate key definitions per table 10
- Supported column types Decimal Number, Whole Number, Single Line of Text, Date Time, Lookup, Option Set
- Field-level security Not allowed on key columns
Virtual tables Alternate keys are not supported , because uniqueness can't be enforced on data that lives in another system
Keys are created through the table designer or programmatically with EntityKeyMetadata and CreateEntityKey ; because building the underlying index can take time on a table with existing data, index creation runs as a background job you can monitor through EntityKeyIndexStatus (Pending, In Progress, Active, Failed). One practical gotcha: if a key column's value contains characters like / < > * % & : \ ? + , retrieve, update, and upsert operations that reference the key won't work — pick key columns whose values are guaranteed clean if they're going to be used for integration.
Once a table has an alternate key, both the Web API ( accounts(accountnumber='A123') ) and the SDK ( Entity.KeyAttributes , a KeyAttributeCollection ) can reference that record without ever knowing its GUID. Combined with change tracking's ability to say "here's what changed," alternate keys give the external system everything it needs to identify which Dataverse record a changed external record corresponds to — the missing piece that the next section, upsert-based synchronization, ties together into a single write operation.