Dataverse Solution [Complete Tutorial]

Are you familiar with Microsoft Dataverse Solution and its types? No reason for concern. You can learn more about the Dataverse solution, how to build a Power Apps Dataverse solution, and more with the help of this Microsoft Dataverse tutorial.

We’ll also talk about the topics below connected to the Dataverse solution:

• What is Dataverse Solution
• Types of Dataverse Default Solutions
• Working With Power Apps Solutions
• Dataverse Solution Search and Filter
• Dataverse Solution Layers
• How to Create Dataverse Solution
• How to Create Power Apps Model-driven App in Solution
• Dataverse Export Solution
• Dataverse Import Solution
• Power Apps Solution Checker
  • How to Run Power Apps Solution Checker
  • How to Cancel Power Apps Solution Checker
• Power Apps Solution Checker States
• Dataverse Solution Upgrade

What is Dataverse Solution?

• Applications and components are migrated from one environment to another using Dataverse Solutions.
• A solution may have one or more applications in addition to site maps, tables, processes, online resources, choices, flows, and other elements.
• Application lifecycle management (ALM) implementation in Power Apps and other Power Platform products, such as Power Automate, is achieved through solutions.

Types of Dataverse Default Solutions

There are two types of Default solutions in Power Apps Dataverse. Such as:

• Common Data Service Default Solution:

When you want to check out or learn Power Apps, the Common Data Service Default Solution is helpful. For their environment customizations, producers have access to this solution by default.

• Default Solution:

This unique solution includes each and every part of the system. The default approach is helpful for finding all the details and setups in your system.

Also, read: Dataverse Create Table [With Examples]

Working With Power Apps Solutions

You may explore a list of options in Power Apps by choosing Solutions from the left menu. Refer to the table below for more details:

Option	Description
New solution	Create a solution and complete all your customization to find and use just the components you’ve customized. Following that, you can easily introduce your solution to additional settings.
Import solution	You can import a solution into your environment.
Open AppSource	You may find solutions specialized for your sector that integrate with the items you already use by going to Microsoft AppSource.
Publish all customizations	All current modifications in your environment should be published.
Switch to classic	Run the classic solution explorer.
History	View data about previous solution actions including import, export, and uninstall.

The Power Apps Dataverse solution screen is seen in the image below.

You can choose a solution from the Solutions category to see its elements. By scrolling over the items, you may look into every part of a solution. If the list has more than 100 items, you may choose to load the next 100 to view more.

This is the overview of Power Apps Dataverse Solutions.

Check out: Dataverse create table from SharePoint list

Dataverse Solution Search and Filter

Suppose you want to search for any solution component, then you can search for it in the search bar by its name. Refer to the screenshot below.

Similarly, if you want to filter any solution name, then you can filter it out by using the Display name field. Expand the Display name -> Filter by the name -> Tap on Apply and then the specific solution will filter out as shown below.

This is how to work with Dataverse Solution Search and Filter.

Dataverse Solution Layers

There are two unique layer levels in Dataverse. Such as:

1. Unmanaged layer: There is only one layer in the unmanaged layer. This layer contains all imported unmanaged solutions and unmanaged modifications.
2. Managed layers: The system solution and all imported managed solutions are at this level. When several managed solutions are installed, the most recent one is installed atop the most recent managed solution. This indicates that the second solution deployed can alter the first solution installed. The managed solution that follows the one that is uninstalled takes effect. The default behavior specified in the system solution is used if all managed solutions are uninstalled.

How to Create Dataverse Solution

This section will look at how to build a solution in Power Apps Dataverse. Follow the steps below:

• Sign in to Power Apps.
• Click on Solutions from the left navigation and then tap on + New solution.

• The New solution pane will appear below after you click on it. The fields that are below in this pane must be filled out.

• For a list of pane field descriptions, see the table below.

Field	Explanation
Display name	This represents the name that appears in the list of solutions. Later, you can modify this.
Name	The solution’s unique name. The Display Name column value you give will be used to construct this. Before saving the solution, you can change this, but once saved, changes cannot be made.
Publisher	Either the default publisher or a new publisher can be chosen. In order to use the service consistently in all of your environments, we advise you to create a publisher for your business.
Version	For the version of your solution, provide a number. Only if you export your solution is this relevant. When you export the solution, the version number will appear in the file name.

• Then click on the + New publisher. A publisher of solutions identifies the app’s creator.

• Provide the information below to that New publisher page.

Fields	Description
Display name	The publisher is identified by this name in the solution.
Name	Without spaces or other special characters, this is the name of the internal publisher.
Description	This is an optional field. Provide the description of the new publisher.
Prefix	To distinguish provided Dataverse objects from your custom items, it is applied to all custom solution items.
Choice value prefix	This is an additional numeric value that is added to all internal choice value identifiers. When utilizing Power Automate, they become crucial, but they are not displayed on the application front-end.

• To establish a new publisher and go back to the screen for creating solutions, click Save.

• Fill out the New solution form with the following details now:

1. Display name = Provide a unique solution name.
2. Name = The internal solution name is shown here without any spaces or other characters.
3. Publisher = Select the publisher name (TS Solution) that we have created in the earlier step. Expand it and select the publisher from the dropdown menu.

To build the new solution, click on the Create button.

• Currently, our environment can use our new solution. Once we tap on the new solution, we can view the standard object types, including Apps, Chatbots, Cloud flows, and Tables. The solution screen will appear like the screenshot below.

• We can use things given as part of the Common Data Model or import items we previously developed by selecting Add existing option.

This is how to create Dataverse Solution in Power Apps.

Have a look: Delete All Records From Dataverse Table [With Examples]

How to Create Power Apps Model-driven App in Solution

Now we will see how to create an app with existing or custom tables to track the product details.

• On the Dataverse Solution page, click on Add existing from the top bar and select Table as shown below.

• Select any existing or custom dataverse table (Product Sales) under the Add existing tables page. Additionally, you may use the search box to browse any table. Once you find the specific dataverse table, select it and click on the Next button.

• Click Add after checking the Include all objects option for that particular table. Columns, information, views, forms, keys, business rules, and other things are examples of components.

• Next, we will create a new table by selecting + New and Table as below.

• Click Save after setting the Display name to “Supplier” and choosing Enable attachments (including notes and files). Here, try to name tables in the single because Dataverse will generate a plural name for the table.

• In the Supplier table, create two different columns by using the + New column option. Those columns are:

1. Supplier Name (Single line of text data type)
2. Supplier Contact Number (Whole number)

Once you created it, just click on the Save button.

• Now come back to the Tables section. You can see that the Tables screen has a total of two tables, Product Sales and Supplier.

• After building our data model, we can now design our model-driven app. Go to Apps (from the left navigation) -> Expand + New from top -> App -> Choose Model-driven app.

• On the New model-driven app page, we need to enter the fields below as:

1. Name = Provide a name for the Model-driven app.
2. Description = This is an optional field. Enter the app description.
3. Use components from a custom solution = Once you enable this option, then the Solution and Site map fields will be visible at the bottom of the page.
4. Solution = Choose the most current solution you came up with or any other one that is already in existence.

Finally, click on the Create button.

• Now the model-driven app is ready to use inside the Dataverse solution and it looks like the below. By adding Pages, we can integrate our data model into our app. Pages are the views and forms that are already included with Dataverse and need very little new development to provide the best user experience. Click the + Add page button to open a new page.

• Click Next after selecting Table based view and form as the page type.

• Next, Choose the data table for the pages either Select the existing table or Create new table. Also, you can select one or more tables under the Select one or more tables section. Enable the Show in navigation option and then click on Add button.

• You can see what the model-driven app page looks like in the image below. As we have added one more table i.e. Account, that’s why the app appears with the Account table (including all fields).
• In case you want to change the table, then you can do it from the Table section (right side of the page).

• The app is displaying all the fields and data that are offered within the Product Sales table because we selected it. Make sure to Save and Publish the app under the Power Apps Solution after everything is finished. If not, you risk losing the data.

These are the steps to create a Power Apps Model-driven App in Solution.

Also Read: Dataverse Primary Name Column Autonumber

Dataverse Export Solution

Next comes how we can export the Dataverse solution in Power Apps. Here, we will export the Product Solution that we recently created, which is the same solution mentioned earlier. Follow the steps below:

Step – 1:

In Power Apps, go to Solutions (from the left navigation) -> Select the specific Dataverse or Power Apps solution (Product Solution) -> Click on the vertical ellipses -> Tap on the Export solution. Additionally, as illustrated below, you may select the Export solution option from the page’s top navigation.

Step – 2:

Before exporting, you have two choices to make:

1. Publish all changes: In general, if all of your modifications are finished and ready to be used, this is a good strategy. With this choice, all alterations to our solution items will be promoted.
2. Check for issues: This system check is being done to verify if there are any components that are not ready for usage.

First, click on Publish button and wait for some time once all items to be published. Later, click on the Run button and wait for the issue check to complete. The pane will eventually appear as seen in the image below. For the next step in the procedure, click Next.

Step – 3:

Currently, you may choose to export as:

1. Managed (recommended) = This is useful for transferring tested code to a real-world setting. In the specific environment, the solution’s components cannot be altered.
2. Unmanaged = You can alter the solution’s components anyway you like. Sharing code with others is made easier by this option.

We’ll export in Managed format. Choosing Managed, then click Export.

Step – 4:

You can download the export file after it has been created. To locally store the solution file, click Download as shown below.

Step – 5:

Choose the file name and save it wherever you’d like on your system.

The XML files that allow the solution to be rebuilt may be seen if you look closely at the export file. XML file excerpt seen in the picture below.

These are the steps to export the Dataverse Solution.

Check out: Filter Dataverse Choice Column [With Various Examples]

Dataverse Import Solution

To import the Dataverse solution in the destination environment, follow the steps below:

Step – 1:

In Power Apps, choose the target environment, select Solutions (from the left navigation), and then choose Import solution from the top of the page.

Step – 2:

Select your downloaded export file by clicking Browse. Choose Next.

Step – 3:

The details we gave in the export will be verified on the Import a solution screen (Name, Type, Publisher, Version, and Patch). To start the procedure, click Import.

Step – 4:

The PowerApps Solutions panel allows users to see the import procedure. Keep a look out for the grey banner towards the screen’s top. The import procedure typically takes a few minutes to finish. Once finished, the grey banner will change to green to indicate that the import was successful.

Step – 5:

When you select the Product solution, you’ll see that every one of our items has been replicated in the environment we’ve chosen. Also take notice that since all of the items are a part of a managed solution, we are unable to alter any of them directly. You may now run or play the app to test how the Product app works.

This is all about how to import the dataverse solution in Power Apps.

Check out: How to Upload images to Dataverse from Power Apps

Power Apps Solution Checker

• With the help of the solution checker functionality, you can immediately spot these troubling patterns by doing a thorough static analysis check on your solutions in comparison to a set of recommended practice criteria.
• You receive a thorough report detailing the issues found, the components and code impacted, and links to documentation outlining each issue’s resolution when the check is finished.
• The solution checker evaluates the following solution components:

1. Dataverse custom workflow activities
2. Dataverse web resources (HTML and JavaScript)
3. Dataverse configurations, such as SDK message steps

How to Run Power Apps Solution Checker

Follow these steps to run the solution checker in Power Apps:

• On the Power Apps page, Click on Solutions from the left navigation.
• From the Solutions page, select a solution (Appointment Solution) that you want to run.
• Click on the vertical Elipses (…) and then point to the Solution checker -> Click on the Run option as shown below.

• You can see the solution checker is operating, as shown in the status window at the top of the Solutions page.

Take note of the following:

1. It can take the solution checker a few minutes to finish the analysis.
2. Throughout this period, you will see a Running… status in the Solution list’s Solution check column.
3. You’ll be notified through email and on the Power Apps site’s Notifications section when the check is completed.

When the check is completed, review the report.

This is how to run Power Apps Solution Checker.

How to Cancel Power Apps Solution Checker

• You can cancel the solutions check once it has been submitted in your environment by using the Cancel option.
• Expand the Solution checker from the top command bar and then click on the Cancel button as in the screenshot below.

• The solution check stops working and the status reverts to the initial state when you cancel a check.

This is how to cancel Power Apps Solution Checker.

Read: How to Create Dataverse View

Power Apps Solution Checker States

The Solution check column becomes visible in the Solutions list once the solution checker has been installed in your environment. The solution analysis states for a solution are shown in this column. Refer to the table below:

State	Explanation
Hasn’t been run	Never has the solution been explored.
Running	The solution is being analyzed.
Couldn’t be completed	Analysis of the solution was requested, but it was unsuccessful.
Results as of date and time	The findings of the solution analysis are now available for download.
Couldn’t be completed. Result as of date and time	The most recent analysis request failed to finish. You can download the most recent successful results.
Checked by Microsoft	Microsoft is in charge of this solution. On certain solutions, solution analysis is not authorized.
Checked by Publisher	This is a third-party-managed solution. Currently, solution analysis isn’t available for these solutions.

This table represents the Solution Checker States in Power Apps.

Dataverse Solution Upgrade

To upgrade or update the Dataverse Solution, you can refer to this Power Apps MSDN link: Dataverse Solution Upgrade

Also, you may like some more Dataverse & Power Apps tutorials:

• How To Get Dataverse List Rows Count Using Power Automate
• How to Export Dataverse Table to Excel
• Power Apps Add Data to Dataverse Table
• How to create and use dataflow in Dataverse
• How to Create Dataverse File Field
• Power Apps Sort Gallery [With 15 Useful Examples]
• Power Apps Search SharePoint List Examples
• Power Apps Search Gallery + 19 Examples

This Microsoft Dataverse tutorial teaches every aspect of the Dataverse solution, including what it is and the many types there are. Also, we learnt how to build a Power Apps Dataverse solution, and many more related topics below:

• Types of Dataverse Default Solutions
• Working With Power Apps Solutions
• Dataverse Solution Search and Filter
• Dataverse Solution Layers
• How to Create Dataverse Solution
• How to Create Power Apps Model-driven App in Solution
• Dataverse Export Solution
• Dataverse Import Solution
• Power Apps Solution Checker
  • How to Run Power Apps Solution Checker
  • How to Cancel Power Apps Solution Checker
• Power Apps Solution Checker States
• Dataverse Solution Upgrade