In this next post as part of my series on solution architecture for the Power Platform I’m going to focus the next ALM topic on solution releases and the process we as solution architects should wrap around this. Stay tuned for more content in this series coming up friends!
Importing managed solutions
So friends, when it comes to releasing your solutions as you most certainly already know, they get released to any environment which isn’t development as managed 🙂 …
Don’t just have developers create new solutions for every change you want to apply to your application or solution. Head back to that solution layering strategy you implemented as part of your wider ALM strategy and ensure your developers are working to this.
Import options
So when it comes to importing new managed solutions we have the following options for import…
| Update | Applies the changes in the solution. You cannot delete components by using this option. |
| Upgrade | Imports changes and applies them immediately, including removing components that are not in the new solution, the old solution, and any patches that are removed. |
| Stage for Upgrade | Similar to upgrade, but it pauses after a new solution is imported before you have removed components so that you can do data migration. Then, you can manually trigger the final application of the solution. |
What’s coming up?
So friends stay tuned! In my next post I’ll share some content on starting to automate the release process and relevant processes here using Azure DevOps! This might not be something you apply to all solutions but it’s important you’re aware of the capabilities here and implementation rules as a solution architect.