You create an integration between the Dataverse and Azure SQL database.
You need to be sure that data is in-sync.
What are two options you can use for data syncing and checking for the latest changes?
Click on the arrows to vote for the correct answer
A. B. C. D. E.Correct Answers: B and D
To synchronize the data between the Dataverse and external system, you need to enable the Change tracking option (Number 3) for the tables you want to synchronize.
You can find this option on the table settings blade (Number 1) under the "Create and update settings" section (Number 2).
You can retrieve the data changes using the Delta links.
The Delta links are the tool provided by the OData 4.0 specification.
It works like the date and time tracking stamps.
To see the table's changes, you need to use a Web API and call the Dataverse entity using a special header key: Prefer with “odata.track-changes” as a value.
In response, you will get the deltaLink token.
You can use this token the next time when you want to see the changes since you run your query.
All other options are incorrect.
For more information about the Dataverse change tracking and data synchronization, please visit the below URLs:
To ensure that data is in-sync between Dataverse and Azure SQL database, you can use two options:
To use change tracking, you need to enable it on the Dataverse tables or entities that you want to track. You can then use a tool such as Azure Data Factory or a custom script to extract the changes and synchronize them with your Azure SQL database. Change tracking is a reliable and efficient way to keep your data in-sync between Dataverse and Azure SQL.
To use delta link, you need to enable it on the Dataverse tables or entities that you want to track. You can then use a tool such as Azure Data Factory or a custom script to retrieve the changes and synchronize them with your Azure SQL database. Delta link is a powerful and flexible way to keep your data in-sync between Dataverse and Azure SQL.
Option A (OpenAPI) is a specification for building APIs, and is not directly related to data synchronization between Dataverse and Azure SQL. Option C (Blank custom connector) is a tool for building custom connectors to connect to external services, and is not directly related to data synchronization between Dataverse and Azure SQL. Option E (Postman Collection) is a tool for testing APIs, and is not directly related to data synchronization between Dataverse and Azure SQL.