Solutions - Revision history

CarinaMClaesson at 07:25, 23 December 2021

2021-12-23T07:25:08Z

2021-12-03T13:59:46Z

2021-12-03T13:46:50Z

2021-12-03T13:46:25Z

2021-12-03T13:45:51Z

2021-12-03T10:52:54Z

2021-12-03T10:52:40Z

2021-12-03T08:18:36Z

2021-01-13T19:36:22Z

2021-01-05T08:47:22Z

@@ Line 26: / Line 26: @@
 The first time you import a solution the solution will be created in the target environment. The next time you can choose between doing an Upgrade or Update, the difference is that with an Upgrade you will remove all components in the target environment which is not longer in the source environment but was in the Managed Solution before.
-If you want to create a "hotfix" you can create a patch. See page [[How to create a Solution Patch]].
+If you want to create a "hotfix" you can create a patch. See page [[How to work with Solution Patches]].
 == Microsoft Resources ==

@@ Line 1: / Line 1: @@
 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.
 == 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]].
+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]]. There might be circumstances where you will want to have more than one and an example of that is if you use solution components for which the ALM process still is not fully covered. That might mean that it requires some manual steps in the target environment after a deploy and in order to avoid deploying those componentes more than necessary you might want to have such solution components in an own solution.
 {{
@@ Line 18: / Line 12: @@
 }}
-=== Patches ===
+=== Two types of Solutions ===
-TBD
+Solutions can be devided into <b> Managed solutions </b> and <b> Unmanaged solutions</b>.
 == Microsoft Resources ==

@@ Line 15: / Line 15: @@
 PWBoxWarning
 | title = Known limitations
-| text = Sometimes the ALM process for new features that are introduced to the platform are a bit behind the feature. So you might need to do some work-arounds for your ALM story. Read about known limitations when using canvas apps, cloud flows and custom connectors in Solutions [https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/solutions-overview#known-limitations/?WT.mc_id=DX-MVP-5003780 Known limitations here].
+| text = Sometimes the ALM process for new features that are introduced to the platform are a bit behind the feature. So you might need to do some work-arounds for your ALM story. Read about known limitations when using canvas apps, cloud flows and custom connectors in Solutions [https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/solutions-overview#known-limitations/?WT.mc_id=DX-MVP-5003780 here].
 }}

@@ Line 4: / Line 4: @@
 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 ==
@@ Line 17: / Line 11: @@
 Sometimes you might need to do a minor update and then you can create a patch.
 === Patches ===

@@ Line 4: / Line 4: @@
 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 ==
@@ Line 17: / Line 23: @@
 == 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
 [[Category: ALM]]

← Older revision		Revision as of 10:52, 3 December 2021
Line 1:		Line 1:
−	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 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 can be devided into managed solutions and unmanaged solutions.

← Older revision		Revision as of 08:18, 3 December 2021
Line 4:		Line 4:

	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.		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 ==		== Microsoft Resources ==

@@ Line 6: / Line 6: @@
 == Microsoft Resources ==
-[https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm 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 Known limitations] Known limitations when using canvas apps, flows, and custom connectors in solutions
+[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