Skip to content

Commit 2b356cc

Browse files
authored
Merge pull request #10181 from MicrosoftDocs/shmcarth-upgrade
Update update-solutions.md
2 parents 6e61bf8 + 1052888 commit 2b356cc

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

powerapps-docs/maker/data-platform/update-solutions.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,6 +67,9 @@ The procedure to import the updated solution is similar to installing a new mana
6767
**Completing Solution Upgrade**
6868
If you chose to stage for upgrade, or if the system had an issue completing an upgrade, you'll see that you have the original solution still installed in your system as well as a new solution that has the same solution name as the base solution suffixed with \_Upgrade. To complete the upgrade, select the base solution in the solution list and select **Apply Solution Upgrade**. This uninstalls all previous patches and the base solution then rename the \_Upgrade solution to be the same name as the previous base solution. Any components that were in the original solution and patches that aren't present in the \_Upgrade solution will be deleted as part of this process.
6969

70+
> [!NOTE]
71+
> Recent changes in the platform have optimized the single step upgrade process to no longer use a temporary _Upgrade solution or use an uninstall operation on the original solution.
72+
7073
## Understanding version numbers for updates
7174

7275
A solution's version has the following format: major.minor.build.revision. An update must have a higher major, minor, build, or revision number than the parent solution. For example, for a base solution version 3.1.5.7, a small update could be a version 3.1.5.8 or a slightly more significant update could have version 3.1.7.0. A substantially more significant update could be version 3.2.0.0.

0 commit comments

Comments
 (0)