PL 400 : read entity change records by using platform APIs (Implement data synchronization)

We have discussed about Change tracking in the previous article. It has given information about the behavior and its usefulness. As is known, change tracking is used for the purpose of synchronizing the data by identifying the data changes that have occurred since the last data synchronization. It provides the efficient and reliable mechanism to determine what records had changed in Dataverse.


Before the read the changes for a table, make sure that the change tracking feature is enabled in that table. Either developers can change from Table UI or programmatically by setting the ChangeTrackingEnabled property to True.

Delta links:

According to the OData 4.0 documentation, delta links are "opaque, service-generated links that the client uses to retrieve subsequent changes to a result". Microsoft has built this standard into change tracking in Dataverse to provide a common, standard method for interfacing with change data as it occurs over time. After issuing a change tracking request, our response will contain a delta link, which we will then pass to our next request to get changes that have occurred since the initial request.

Read changes in tables by using the Web API:

After enabled change tracking on an table, we can retrieve its changes through the Web API by adding odata.track-changes as a preference header in web request. On the initial request, we will receive the entire set of data that applies to the query because a delta has not been applied. However, the response will show an @odata.deltaLink value. This link contains a Dettatoken parameter which is intended to be passed into subsequent when we want to see what changes have been applied since this query was run.


Code:

{

          "@odata.context":"[Organization URI]/data/v9.0/$metadata#accounts(name,telephone1,fax)/$delta",

          "@odata.deltaLink":"[Organization URI]/api/data/v9.1/accounts?$select=name,telephone1,fax&$deltatoken=919058%2108%2f22%2f2017%2008%3a21%3a20",

"value":

    [

        {

            "@odata.etag":"W/\"915244\"",

            "name":"Monte Orton",

            "telephone1":"555000",

            "fax":"10101",

            "accountid":"60c4e274-0d87-e711-80e5-00155db19e6d"

        },

        {

            "@odata.context":"[Organization URI]/api/data/v9.0/$metadata#accounts/$deletedEntity",

            "id":"2e451703-c686-e711-80e5-00155db19e6d",

            "reason":"deleted"

        }

    ]

}


Courtesy :

Change Tracking 


Comments

Post a Comment

Popular posts from this blog

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power ...
Read more

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more