Question

You are building a nightly synchronization process that copies new and updated Account records from Dataverse to an external reporting database. Change tracking is enabled on the Account table. On the first run you must retrieve all records and store a marker so that subsequent runs return only the records that changed since the previous run. Which Dataverse Web API request technique correctly retrieves the incremental changes on later runs?

Accepted Answer

Add the 'Prefer: odata.track-changes' header to the account query, persist the returned @odata.deltaLink, and call that delta link URL on subsequent runs.

Answer

Send a RetrieveMultiple query with an ORDER BY on the modifiedon column and store the highest modifiedon value to filter the next run.

Answer

Enable auditing on the Account table and read the audit history entities to determine which records changed.

Answer

Use the RetrieveRecordChangeHistoryRequest for each Account to detect field-level changes since the last sync.