PL 400 : configure entity change tracking (Implement data synchronization)

Data is fuel in the business world and companies always try to maintain data accuracy and integrity. Data synchronization is the essential process of establishing consistency between data from a source to a target data storage. Such data has a huge impact on sales, decision making and customer retention. Example read leads from csv files and write to CRM or find new accounts in ERP system and insert/update  into CRM.
Data synchronization means maintaining consistency between the source and the target.



Microsoft Dataverse provides several mechanisms for synchronizing and integrating data. Change tracking is one of them. Such a mechanism is available in SQL Server and other databases. Microsoft Dataverse is a special type of database that provides the capability of business automation and database features. Change Tracking is used for the purpose of keeping data synchronized by identifying the data changes that have taken place since the last data synchronization was performed.

By default, Change Tracking is enabled for out of box tables, but need to enable for custom tables.

Generally, large Dataverse synchronize their data with an external data source. Business users can synchronize specific datasets with external data sources or warehouses. Change tracking reduces the load on server resources and saves processing time when extracting Dataverse data and synchronizing it to external sources. Change tracking is used for the purpose of synchronizing data by identifying data changes that have occurred since the last data synchronization.

To configure entity (table) change tracking:
  • Go to https://make.powerapps.com/ >  Choose the Dataverse
  • Select an Table, and under Setting, Edit Table will open
  • Click Advanced Option 
  • Select  Track Changes check box.




Comments

Post a Comment

Popular posts from this blog

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

Is Debt Prosperity or Trap?

 “What can be added to the happiness of a man who is in health, out of debt, and has a clear conscience?”  Adam Smith Grandfather Bhishma lay on the bed of arrows and was preaching the future king of Hastinapur about political science, economics and the duties of the king. He took a deep breath and told Yudhishthira " Fire, debt and enemies must be dealt with quickly and completely. If there is any balance left, they can continue to grow. " The future king was listening with curiosity and was eager to learn about the complete knowledge from his grandsire. Each moment was important as the sun was moving from south to north. Either we read the quote of the father of modern economics or both ancient great scholars are advising to avoid debt. But the whole of modern economics is based on the debt that advises the public to borrow money. The aggressive campaign of banks and financial institutions has been luring more and more loans. Even democratic governments and public banks con
Read more

Exam PL-400: Microsoft Power Platform Developer

 Create a technical design (10-15%) Validate requirements and design technical architecture design and validate the technical architecture for a solution design authentication and authorization strategy determine whether you can meet requirements with out-of-the-box functionality determine when to use Logic Apps versus Power Automate flows determine when to use serverless computing, plug-ins, or Power Automate determine when to build a virtual entity data source provider and when to use connectors Design solution components design a data model design Power Apps reusable components design custom connectors design server-side components Describe Microsoft Power Platform extensibility points describe Power Virtual Agents extensibility points including Bot Framework skills and Power Automate flows describe Power BI extensibility points including Power BI APIs, custom visuals, and embedding Power BI apps in websites and other applications describe Power Apps portal extensibility points incl
Read more