Importing Managed Solutions - What has changed to the Upgrade verses Update Process?

When deploying managed solutions to Power Platform, there are multiple options you can choose from. In this episode of the Low Code Revolution, Scott Durow is joined by Shan McArthur who explains when to use each option, the differences between them, and some changes being rolled out that you may not be aware of.
Chapters:
00:00 Introduction
03:46 Managed vs Unmanaged solutions
06:25 Options available when importing managed solutions
11:39 Current recommendations
12:37 What are patches and why avoid them?
15:13 What is changing and what are the new recommendations
19:17 When are the changes rolling out?
Resources:
For more information on Application Lifecycle Management in Power Platform, visit aka.ms/pp/alm
#PowerPlatformAdvocates #PowerApps #LowCodeRevolution

[@JumpUpJumpUpandPowerPlatform]

A synopsis: Always use 'Upgrade'. In the next few weeks, it'll be just as quick as using 'Update'.

[@martintolk3820]

Perfect, will greatly reduce complexity in pipeline. Makes using one big solution more attractive and allows leveraging the "preferred solution" feature more broadly

[@xRMInsights]

Absolutely brilliant episode! Such a clear explanation and super helpful for a number of projects I’m working on 👍🏼 Can’t wait to hear more about the topics you mentioned towards the end - Joel

[@hhappy]

Thanks Scottt and Shan. Looking forward to the in-place stage and upgrade. Sounds like it could a real speed improvement.

[@jhnndctt]

Awesome! Will be watching for a future episode re solution segmentation.

[@chrisban2512]

Thanks for this! It will help so much with faster releases.

[@chrisban2512]

Also can we still see changed layers with upgrade option?

[@RonDeGiusti]

There is still a business pain that patches seem to solve: How do I release a hot fix for my solution while the project team continues to work on new features. It seems like patches may still be the best way to handle those. If patches are to be avoided, then how do we release hot fixes while the project team continues to work on new functionality?

[@michaelfpereira]

Hello! I'm using the approach tô create an hotfix solution. It is a small solution that has the fixes, i deploy quickly on the target environment. In the next release i cleanup in my dev environment and remove on the deployment process, because the fixes already been ton the correct solutions. This is the way that is faster and you can manage well the solutions

[@Nor5eman]

Fantastic!

[@wouterkessener2811]

Thanks Shan and Scott, great stuff coming. Still a bit confused on the Patch part. Between the lines I hear you say patches are not best practices in the future, because there are no benefits considering the speed of releasing. But how to handle Hot Fixes to prod. For example. Dev has feature A and B in the works, both not finished for release. Now PROD needs a small hotfix ( cannot wait for A en B to be finished in Dev) . Wondering how to handle that without using a patch.

[@chandanasasi5469]

How to change the connections for a managed solution.?

[@ryanperrymba]

Awesome. What happens if this throws an error mid upgrade? Without the additional layer, would it be possible to roll back? Or do we need to / will it lock out / pause user requests during the upgrade? IE updates to the system are treated as an all-or nothing transaction - what about Flows, etc. that tie into other resources?

[@simonpurdy2496]

Will this also happen within the package deployer tool? So used to doing pac package deploy...

[@mlbb4372]

Hello, I bought a laptop, Windows 11 version is available, 512 GB SSD, i5 processor, 8 GB RAM, it starts at 45% and 50% in the task manager and it is very high. If there is no problem with the device, Windows 11 takes up too much RAM and needs to be fixed. Have a good day.