You modified a solution in a development environment.
You want to clone the solution and import it to the test environment.
Your current solution version is 5.2.3.1
What will be the version of the cloned solution?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C
There are two options for the managed Dataverse solutions updates: To create a patch - a bug fix or some minor solution change.
To clone - a major solution update.
You can select a solution from the Power Apps portal and click on the three dots for more options.
When you choose the Clone menu item, you will see two options: Clone a patch and Clone a solution.
Every solution has a version number with the following structure: <major>.<minor>.<build>.<revision>
The “Clone solution” controls the first two numbers: <major> and <minor>
The Power Platform automatically increments the minor number, e.g., if the basic solution has a 5.2.3.1 version (Number 1), the clone will have by default 5.3.0.0 (Number 2)
Users can change the first two numbers only.
The “Clone a patch” controls the last two numbers: <build> and <revision>
The Power Platform automatically increments the build number, e.g., if the basic solution has a 5.2.3.1 version (Number 1), the patch will have by default 5.2.4.1 (Number 3)
Users can change the last two numbers only.
All other options are incorrect.
For more information about cloning the Dataverse solutions, please visit the below URLs:
When cloning a solution in Microsoft Power Platform, the version of the cloned solution will depend on the versioning options selected during the cloning process.
By default, when cloning a solution, the "Create a new solution version" option is selected. This means that a new version of the solution will be created in the target environment with a version number that is one minor version number higher than the source solution.
In this case, the current solution version is 5.2.3.1. If this solution is cloned with the default options, the version of the cloned solution will be 5.2.4.0, with a build number of 0.
However, there is also an option to manually specify the version number of the cloned solution during the cloning process. If this option is used, the version of the cloned solution can be set to any valid version number.
Given the available answer options, none of them match the default versioning behavior of cloning a solution with the "Create a new solution version" option selected. Therefore, it's likely that the solution was cloned with a custom version number.
Without additional information about the versioning options used during the cloning process, it's impossible to determine the correct answer.