Data Syncing and Change Tracking Options for Dataverse and Azure SQL Database Integration | PL-400 Exam

Data Syncing and Change Tracking Options

Prev Question Next Question

Question

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?

Answers

Explanations

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).

| Edit table @ x Display name * | PC Manufactures | Plural display name * | PC Manufactures | Name* (@ ¢ cr437_ PCManufactures Enable attachments (including notes and files) Fewer settings “~ > Description > Table type > Collaboration Y Create and update settings @ Enable quick create forms @ Duplicate detection @ Enable change tracking © © > Offline Done Cancel

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.

"id": "c84cb573-f476-4c0d-9bcf-f3dd5ab1317e", "acceptMappedClaims": null, "accessTokenAcceptedVersion": null, "addins": [], "allowPublicCli "appiId": '"eQ6008c9-775c—41e8-960f-49bf383d46a2", "appRoles": [], "oauth2AllowUrlPathMatching": false, "createdDateTime": "2021-@4-17T06:29:57Z", "disabledByMicrosoftStatus": null, "groupMembershipClaims": null, "identifierUris": [GD], "informationalUrls": { GD}, "keyCredentials": [], "knownClientApplications": [], "LogoUrl": null, "LogoutUrl": null, "name": "CBFunctionAppAsAPI",

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, there are two options that you can use for data syncing and checking for the latest changes:

  1. Change Tracking: Change tracking is a feature in Dataverse that enables developers to monitor changes to records in an entity. When a record is created, updated, or deleted in an entity, a change event is generated. These change events can be used to synchronize data with external systems such as Azure SQL database. You can configure change tracking in Dataverse using the Power Apps CLI or through the Power Platform admin center.

  2. Delta Link: Delta link is a feature in Dataverse that allows you to retrieve only the changes that have occurred since the last time you queried the entity data. Delta link works by returning a token that represents the state of the data at the time of the query. The next time you query the data, you can pass this token to the API to retrieve only the changes that have occurred since the last query. Delta link can be used to synchronize data with external systems such as Azure SQL database.

Options A, C, and E are not relevant for data syncing between Dataverse and Azure SQL database. OpenAPI is a specification for building APIs, not a data syncing mechanism. Blank custom connector and Postman Collection are tools for building custom connectors to external systems, but they are not directly related to data syncing.

Therefore, the correct answers are B (Change tracking) and D (Delta link).

Prev Question Next Question