Microsoft Power Platform Developer: Cloning a Solution Version for Test Environment

Cloned Solution Version: 5.2.3.1

Question

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?

Answers

Explanations

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.

Aa

Hb CREATE NEW CONNECTION G RELOAD ORGANIZATIONS | (REPLAY PL

vvrwvwrowrewrowreowreowrowreyws»y

CBTrial x

[iRegister + [QView ~» x Uninstall Profiler £4 Debug [% Unn

Registered Plugins & Custom Workflow Activities

@ (Assembly) Microsoft.Dynamics.AppModule.Plugins

@ (Assembly) Microsoft. Dynamics.CDS.AuthorizationCorePlugins
@ (Assembly) Microsoft. Dynamics.CDS.MetadataExtensionPlugins
@ (Assembly) Microsoft.Dynamics.CDS.PSqlPlugins

@% (Assembly) Microsoft.Dynamics.ComponentHistory.Plugins

@ (Assembly) Microsoft.Dynamics.Enterprise.Connectors.Plugin

% (Assembly) Microsoft. Dynamics.EnvironmentVariables.Plugins

@ (Assembly) Microsoft. Dynamics.KMOnlineFeatures.Plugins

@ (Assembly) Microsoft.Dynamics.KnowledgeArticleFeatures.Plugins
@ (Assembly) Microsoft. Dynamics.MicrosoftFlow.Plugins

@ (Assembly) Microsoft.Dynamics.PowerAppsChecker.Plugins

@ (Assembly) Microsoft. Dynamics.PowerPlatformConnectionReferences.Plug

Properties Details

Register New Assembly

Step 1: Specify the location of the assembly to analyze |
C:\Users\AndreiSergeev\OneDrive - CloudBreezy\Dev\Power Platform\Power Apps\PowerApps

Load Assembly

Step 2: Select the plugin and workflow activities to register
Vv Select All / Deselect All

@ (Assembly) FollowupPlugin

v7) Tm} (Plugin) PowerApps.Samples.FollowupPlugin - Isolatable

Step 3: Specify the isolation mode

@) Sandbox ©

None

Step 4: Specify the location where the assembly should be stored

@) Database @ 7
Disk

GAC

Step 5: Log

|

Register Selected Plugins Close Bn: |

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.

rie | lel Eek Save and Close =, =} Show Dependencies | Export Solution PeTransiations ~ | |g} Publish All Customizations 4, Actions + (@Help +

‘ Solution: Default Solution Oo
[¥ «2 Plug-in Assemblies

Solution Default Solution

Component Type Plug-in Assembly v View Customizable v
YF Information
fg Components
& Entities O Name “ Version Culture Public Key Token Isolation Mad...| Created On Modified On Y Oo
BI option sets
*®| Client Extensions
[9] Web Resources

+a How to Register Assemblies X Delete 3 Show Dependencies = Solution Layers (Sf Managed Properties More Actions ~

Pro Microsoft.CDS.ApplicationUser.Plugins 1.0.0.0 neutral 31bf3856ad364e35 None 4/10/2021 8:07 AM 4/10/2021 8:07 AM
S

2 FollowupPlugin Microsoft.CDS.Catalog.Plugins 9.0.0.0 neutral 31bf3856ad364e35 None 4/10/2021 9:01 AM 4/10/2021 9:01 AM

+ Microsoft.CDS.ApplicationUser.Plugins

“i Microsoft.CDS.Catalog. Plugins Microsoft.CDS.CustomAPI.Plugins 9.0.0.0 neutral 31bf3856ad364e35 None 4/10/2021 9:02 AM 4/10/2021 9:02 AM

~G@ Microsoft.CDS.CustomAPI.Plugins i

+ Microsoft.CDS. DataLakeWorkspaces. Plugins 1 Microsoft.CDS.OrganizationDataSync.Plugins 1.0.0.0 neutral 31bf3856ad364e35 Sandbox 4/10/2021 9:05 AM 4/10/2021 9:05 AM

+a Microsoft.CDS.OrganizationDataSync.Plugins

+i Microsoft. Dynamics.AppModule. Plugins Microsoft. Dynamics.ComponentHistory.Plugins 9.0.0.0 neutral 31bf3856ad364e35 None 4/10/2021 7:50 AM 4/10/2021 7:50 AM

+ Microsoft.Dynamics.ComponentHistory. Plugins

+ Microsoft. Dynamics.KMOnlineFeatures.Plugins Microsoft. Dynamics.KMOnlineFeatures.Plugins 9.1.0.0 neutral 31bf3856ad364e35 Sandbox 4/10/2021 8:51 AM 4/10/2021 8:51 AM

+ Microsoft.Dynamics.KnowledgeArticleFeatures.Plugins

“Gi Microsoft. Dynamics.PowerAppsChecker. Plugins Microsoft.Dynamics.KnowledgeArticleFeatures.Plugins 9.1.0.0 neutral 31bf3856ad364e35 None 4/10/2021 8:53 AM 4/10/2021 8:53 AM

+ Microsoft.Dynamics.PowerPlatformConnectionReferenc...

+ Microsoft. Dynamics.PowerVA.Plugins Microsoft. Dynamics.PowerAppsChecker. Plugins 9.0.0.1 neutral 31bf3856ad364e35 None 4/10/2021 9:27 AM 4/10/2021 9:27 AM

+ Microsoft. Dynamics.ServiceManagementControlsExten...

7G Microsoft. Dynamics.SLAManagement.Plugins Microsoft.Dynamics.PowerPlatformConnectionReferen... 1.0.0.0 neutral 31bf3856ad364e35 None 4/10/2021 8:19 AM 4/10/2021 8:19 AM

+ Microsoft.Dynamics.SolutionComponentConfiguration....

iad ete yrratiis SOu rote yg Microsoft. Dynamics.PowerVA. Plugins 1.0.0.0 neutral 31bf3856ad364e35 None 4/10/2021 8:23 AM 4/17/2021 12:49 AM

Gj Microsoft. Dynamics.SolutionPackageMapping. Plugins

sie Microsote: Dynamics solution sur mary Fuqiis Microsoft.Dynamics.ServiceManagementControlsExten... 9.1.0.0 neutral 31bf3856ad364e35 None 4/10/2021 8:45 AM 4/10/2021 8:45 AM

+ Microsoft.Dynamics.UCICalendar.Plugins
+i Microsoft.Xrm,DataProvider.JsonConverter.Plugins 1-23 of 23 (0 selected) rr Page 1 >

All other options are incorrect.

For more information about cloning the Dataverse solutions, please visit the below URLs:

When you clone a solution in Power Platform, a new solution is created with the same components and settings as the original solution. However, the version number of the cloned solution may be different from the original solution, depending on the cloning settings you choose.

By default, when you clone a solution, the cloned solution will have a new version number, with the major and minor versions incremented by 1, and the revision and build numbers reset to 0. This is to indicate that the cloned solution is a new version of the original solution.

In this case, the original solution version is 5.2.3.1. If you clone the solution using the default settings, the cloned solution will have the version number 5.3.0.0. This is because the major and minor versions are incremented by 1, and the revision and build numbers are reset to 0.

Option A (5.2.3.2) is not correct, as the revision number is incremented by 1 instead of being reset to 0.

Option B (5.2.4.1) is also not correct, as the major and minor versions are not incremented by 1.

Option D (5.3.3.2) is not correct, as the build number is not carried over from the original solution.

Therefore, the correct answer is C (5.3.0.0).