Fixing Managed Solution Version Number in Dataverse
Image Source: Shutterstock.com
Microsoft Dataverse
Sep 26, 2023 8:05 AM

Fixing Managed Solution Version Number in Dataverse

by HubSite 365 about Temmy Wahyu Raharjo

Citizen DeveloperMicrosoft DataverseDynamics 365M365 Hot NewsPower DevOps

Learn how to manage and rectify version number errors in Microsofts Dataverse Managed Solutions with expert advice.

A Fresh Look into Managing Solution Versions in Microsoft Dataverse

The blog post, penned by Temmy Wahyu Raharjo, unravels the process of managing solutions within an intuitive, dynamic environment like the Microsoft Dataverse. Raharjo's company relies on a decoupling model that separates solutions based on component types. The solutions are labeled under specific brackets such as WebResources, Plugins, Customizations, and so forth.

Such a model caters to better tracking of changes, especially for those unrelated to Form, Metadata, and similar elements. It particularly speeds up the import time of a full solution. However, it does come with demerits, such as the necessity of a certain sequence for importing – usually, WebResources first, followed by Plugins, and finally, the Customizations.

Illustrating a recent problem, Raharjo narrates a situation where after manually importing a full WebResource solution, he accidentally updated it to an incorrect version number. Despite displaying the mistake in the informational dialog box, he overlooked it and moved ahead with the deployment, leading to a subsequent problem. When trying to import the correct version number post this, he encountered a stopper error – “The solution being imported for upgrade must have a higher version number than the existing solution.“.

Given their operations model, a mere uninstallation wasn’t plausible as the Customizations solution depended on the WebResources solution. Busting the issue as not a colossal one, Raharjo explains how it can be fixed by increasing the version number incrementally, from 1.0.202230113.1 to 1.1.20230113.1.

By employing Power Platform CLI tools, and following a systematic path (namely creating a connection to the environment where the solution version is incorrect, exporting the solution bearing the right version number, and finally, importing the solution using Power Platform CLI tools), the version can be effortlessly corrected.

Raharjo's anecdote successfully underlines the necessity of meticulous version control and the paradoxical robustness & fragility of managing tools within complex environments like the Microsoft Dataverse.

For more specific insights, you can follow this link.

General Overview

Managing solution versions is a nuanced process that requires deep understanding of the environment where solutions are being built and deployed, such as Microsoft's cloud-based tool. A mistyped version number may seem like a minor error, but it can cause serious repercussions if ignored. These can be mitigated by using automatic version numbering in DevOps pipelines and validated version control approaches. The Power Platform CLI tools, as demonstrated by Raharjo, serve as a solid support system for managing these tasks. While these tools simplify the process, a mindful, alert approach is critical to avoid potential complications, especially in larger system environments.

Read the full article Dataverse: How to fix Managed Solution Version Number

Microsoft Dataverse - Guide to Fixing Managed Solution Version Number in Dataverse

Learn about Dataverse: How to fix Managed Solution Version Number

Microsoft Dataverse, formerly known as Common Data Service, has an essential feature termed Managed Solution versioning. This functionality is commonly utilized in enterprise environments to keep track of and control various components such as Web Resources, Plugins, and Customizations, amongst others. The aspect that stands out is the possibility to manage and track changes efficiently, especially if you are using solutions packager's results.

The primary advantage of separating solutions based on component types is that unrelated changes to Forms, Metadata, etc., don't slow down your import times, particularly for full solutions. Nonetheless, one of the challenges is organizing the import sequence, which typically begins with Web Resources, followed by Plugins and concluding with Customizations.

Despite its benefits, we might end up with occasional mishaps, like wrong version numbers during manual imports. This error can block further imports of correct versions as it states, "The solution being imported for upgrade must have a higher version number than the existing solution." Given the intertwined nature of solutions, where the Customizations solution depends on the WebResources solution, it's not feasible to merely uninstall (roll back) the solutions. So, here arises the need for an effective solution.

Indeed, this problem isn't a significant issue as it relies on just the version number. An optimal solution is to initiate a new version from, for example, 1.0.202230113.1 to 1.1.20230113.1, and it will work. Moreover, if your DevOps pipeline already has automatic version numbering, changing the version number is not a complicated task.

To fix the problem, you would first need to install Power Platform CLI (Command Line Interface) tools. Then, create a connection to the Environment where the solution version is incorrect using the command "pac auth create". Make sure this environment is chosen before proceeding to the next step "pac auth select". After this, export the solution with the correct version number.

Subsequently, import the solution using Power Platform CLI tools via the command "pac solutions import". Once you finish the import process, and voila, the version reverts to the appropriate number. You can confirm this in your settings.

Keep in mind that Microsoft's Power Platform offers a broad range of tools and features that help address a plethora of scenarios, including such versioning mishaps. Happy CRM-ing!

More links on about Dataverse: How to fix Managed Solution Version Number

Dataverse: How to fix Managed Solution Version Number
Jan 13, 2023 — You need to install Power Platform CLI tools. Create the connection to the Environment where the solution version is wrong using “pac auth ...
Upgrade or update a solution - Power Apps
Aug 30, 2023 — Increment the version number when you export the solution as a managed solution. More information: Understanding version numbers for updates.
Dataverse: How to fix Managed Solution Version Number
Jan 14, 2023 — Let's talk a bit about Solutions management. In my current company, we separate out the solutions based on the component types.

Keywords

Dataverse solution, fix Managed Solution, Version Number, Microsoft Dynamics 365, Updating Managed Solution, Dataverse Version Control, Dataverse troubleshooting, Managed Solution problems, Solve Dataverse issues, Dynamics 365 Version Number issues