Dataverse V-Table: Ultimate Import/Export Guide 2024

Key insights

Dataverse: Export-Import Solution for Virtual Table is a guide for configuring, exporting, and importing Virtual Tables from SQL databases to different environments. It starts with preparing the target database by generating scripts in SSMS and running them in a new Azure SQL DB.

The preparation of the Dataverse solution includes adding existing Virtual Tables to a new solution with the option "Include all objects". It is essential to add the corresponding Virtual Table data source and a SQL Connection Reference through the Connection Reference section.

Additional components for business logic, such as Plugin Packages and Plugin Steps, need to be included in the solution. These steps prepare the solution for export, which can then be imported into another environment through the make.powerapps.com portal with the correct SQL Server Authentication details.

After importing the solution, it is critical to update the "Virtual Connector Data Source" to adapt to the new SQL DB environment. It is also important to note that when re-importing a solution, the Dataset Value may revert to its default and needs to be manually adjusted unless the component is removed or updated separately.

• Understanding of Virtual Table configuration and migration between SQL DB and Dataverse environments.
• Preparation of target database and Dataverse solution for export includes generating scripts and adding necessary data sources and references.
• Export-ready solution comprises components such as Virtual Tables, Connection References, Plugin Packages, and Plugin Steps.
• Import process through make.powerapps.com requires authentication updates for SQL Server.
• Post-import necessity to adjust the "Virtual Connector Data Source" in the solution to match the new environment settings.

Dataverse and Virtual Tables

Microsoft's Dataverse is an essential tool for data management and interoperability within the Power Platform ecosystem, including Dynamics 365 and Power Apps. Virtual Tables, or Virtual Entities, are a key feature, allowing seamless integration between Dataverse and external databases, such as SQL. This functionality is particularly important for organizations looking to enhance their business solution infrastructures with dynamic and interconnected systems. The ability to export and import solutions with Virtual Tables simplifies the process of maintaining consistent data across different environments, improving data accuracy and access. Developers find this feature handy to rapidly deploy and update data structures without compromising on the data already in use.

The blog post by Temmy Wahyu Raharjo delves into the intricacies of working with Virtual Tables in Microsoft Dataverse. In a previous session, they covered how to configure a Virtual Table to mirror data from an SQL Database. This time, they explore the process of preparing to export and then import this solution across different environments.

The first step in the process requires setting up the target database. Using SQL Server Management Studio (SSMS), you connect to your development database, generate scripts for the desired objects, and execute these scripts in a new Azure SQL Database. The author emphasizes the simplicity of generating scripts directly to a new query window.

Subsequently, you construct your Microsoft Dataverse solution by adding the existing Virtual Tables, ensuring that "Include all objects" is selected for table inclusion. Additionally, it's important to include the previously created Virtual Table data source, the SQL Connection Reference, and to integrate business logic crafted through plugins.

After adding the necessary components, including Plugin Packages and steps, the solution is ready for export. The import process involves navigating to the Power Apps platform, choosing the target environment, and importing the solution file. You'll be prompted to establish the connection, where you specify the SQL Server name, database, and authentication credentials.

Following the import, you must update the "Virtual Connector Data Source" to align with the new SQL Database. This entails modifying the Dataset Value within the "Advanced Settings" to reflect the target environment. Raharjo cautions that re-importing the solution may reset the Dataset Value to its original state, and manual updating might be required.

The post concludes with testing the configured plugin and a summary snapshot of the necessary components for the Microsoft Dataverse solution export-import process, note that plugins are optional. Raharjo signs off with a salute to the CRM community, underscoring their continuous learning journey and advocacy for clean, human-readable code.