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

Powering Up Your Analytics: Exploring Power Query in Power BI

Image
Data is a valuable asset that has a profound impact on almost every aspect of modern life. Its proper collection, analysis and application can promote innovation, improve efficiency and solve complex challenges in various sectors. In data processing, ETL is a comprehensive process that includes data extraction, transformation, and loading, while Power Query is a specific tool that facilitates the "extract" and "transformation" aspects of ETL, allowing data to be collected and analyzed. Permission is granted to process. And reporting. is ready. It becomes easy to do this. Microsoft's ecosystem of products. Power Query is a data transformation and data preparation engine. Power Query is available in Microsoft Excel and Power BI. Power Query provides a user-friendly and intuitive interface for data professionals and analysts to access and manipulate data from various sources without the need for extensive coding or scripting. It allows users to connect to a wide ra
Read more

Power App Component Overview : Canvas App vs Model-Driven App

Image
The Power Platform is a suite of low-code/No-code tools and technologies developed by Microsoft and Power App is integral component of Power Platform. Power App is platform that enables users to build custom web and mobile applications with a visual interface and minimal coding. The platform support various data sources, including Microsoft 365, Azure Service, and many other, enabling users to integrate and interact with their existing data and systems. In Microsoft's Power Apps, there are two main types of apps that we can create: Canvas Apps: Canvas apps provide a blank canvas where you can design highly customizable applications with a drag-and-drop interface.  Model-Driven Apps: Model-driven apps are built on top of the Dataverse, which provides a set of pre-built data entities and business logic. There are few key technical difference between Canvas App and Model Driven App: During the usability analysis, these high-level technical differences need to be considered. The choi
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