Difference between revisions of "Solutions"
| Line 16: | Line 16: | ||
== Microsoft Resources == | == Microsoft Resources == | ||
| − | [https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm/?WT.mc_id=DX-MVP-5003780 Solutions Concepts] Solutions in Microsoft Docs | + | * [https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm/?WT.mc_id=DX-MVP-5003780 Solutions Concepts] Solutions in Microsoft Docs |
| + | * [https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/solutions-overview#known-limitations/?WT.mc_id=DX-MVP-5003780 Known limitations] Known limitations when using canvas apps, flows, and custom connectors in solutions | ||
| − | [ | + | [[Category: ALM]] |
Revision as of 10:52, 3 December 2021
Solutions are a part of the ALM for the Power Platform. Use solutions in order to gather different parts such as entities, apps, flows etc. and move those artifacts between environments.
Solutions can be devided into managed solutions and unmanaged solutions.
Solutions is a concept which comes from the Microsoft Dynamics CRM platform. Over the years there have been different opinions in the community whether to use managed solutions or not. According to Microsoft unmanaged solutions are intended for development environments only and managed solutions are intended for all other environments such as test and production.
Solution Concepts
Using Solutions you can start with your app development in a Development environment, then move to a Test and eventually to Production. Also see Environment Strategy.
It's best practice to have ONE unmanaged solution per environment and include all your components in that solution in order to avoid dependencies issues during deployment.
Sometimes you might need to do a minor update and then you can create a patch.
Patches
TBD
Microsoft Resources
- Solutions Concepts Solutions in Microsoft Docs
- Known limitations Known limitations when using canvas apps, flows, and custom connectors in solutions