How to work with Solution Patches - Revision history

Benedikt at 22:03, 22 December 2021

2021-12-22T22:03:48Z

Benedikt at 22:03, 22 December 2021

2021-12-22T22:03:25Z

CarinaMClaesson at 15:41, 21 December 2021

2021-12-21T15:41:46Z

CarinaMClaesson at 15:41, 21 December 2021

2021-12-21T15:41:30Z

CarinaMClaesson at 15:33, 21 December 2021

2021-12-21T15:33:51Z

CarinaMClaesson at 20:36, 17 December 2021

2021-12-17T20:36:16Z

CarinaMClaesson: Created page with "Sometimes when working with Solutions you might not need a full deployment of the whole solution, here patches come in. Imagine that you have your solution live in a product..."

2021-12-17T20:34:59Z

Created page with "Sometimes when working with Solutions you might not need a full deployment of the whole solution, here patches come in. Imagine that you have your solution live in a product..."

New page

Sometimes when working with Solutions you might not need a full deployment of the whole solution, here patches come in.

Imagine that you have your solution live in a production environment and you are about to start a new big project. During this project it might be the case that you need to do a smaller update/fix in the production environment, but you will not be able to do that from the DEV environment where you are working with your big new project. Because there will be changes you do not want to add to production yet. In the future you could potentially use Settings for this, but for now and an alternative approach is to make a copy of DEV to another environment before you start with your new project. In that temporarily DEV environment you could do the small fix and create a patch to import to the production environment.

More to add here... We'll continue soon!

@@ Line 14: / Line 14: @@
 You can't do a full deployment since you would deploy changes that aren't tested or approved yet. In this case, you could create a patch, only containing your hotfix, and deploy that.
-Another problem could arise though. Usually, the version of your solution has been changed already when you come to that point, which makes the created patch unusable (because of the mentioned version constraints). A solution to that would be a hotfix environment that contains the same version of your solution as production. Either you have this environment always running or create it when needed from an unmanaged solution which should be stored in your repo (see {{ALM}}).
+Another problem could arise though. Usually, the version of your solution has been changed already when you come to that point, which makes the created patch unusable (because of the mentioned version constraints). A solution to that would be a hotfix environment that contains the same version of your solution as production. Either you have this environment always running or create it when needed from an unmanaged solution which should be stored in your repo (see [[ALM]]).
 == ALM ==

@@ Line 1: / Line 1: @@
-Sometimes when working with Solutions you might not need a full deployment of the whole solution, here patches come in.
+Sometimes you might not need a full deployment of the whole solution, that's where patches come in.
-Imagine that you have your solution live in a production environment and you are about to start a new big project. During this project it might be the case that you need to do a smaller update/fix in the production environment, but you will not be able to do that from the DEV environment where you are working with your big new project. Because there will be changes you do not want to add to production yet. In the future you could potentially use Settings for this, but for now and an alternative approach is to make a copy of DEV to another environment before you start with your new project. In that temporarily DEV environment you could do the small fix and create a patch to import to the production environment.
+== What is a patch ==
-Here follows an example:
+As mentioned a patch is tied to a base solution, to be more specific even to a certain version of it.
-. Make sure it is the same version of the solution in "your new DEV" as in Production. If not, adjust version in "your new DEV".
+Whenever you create or install a new version of the base solution all patches will be rolled up into the base solution.
-. You will then get a new Solution and in that Solution you do the changes you want to do, which are meant to be the "fix for production".
+== Use case ==
-. Import the Patch to Production.
+Another problem could arise though. Usually, the version of your solution has been changed already when you come to that point, which makes the created patch unusable (because of the mentioned version constraints). A solution to that would be a hotfix environment that contains the same version of your solution as production. Either you have this environment always running or create it when needed from an unmanaged solution which should be stored in your repo (see {{ALM}}).
-. Make sure to do the same change in the "real DEV" environment. Either by doing it manually or by adding the components to an unmanaged solution in "your new DEV" and import to "real DEV".
+== ALM ==
-. The next time a deployment of the whole solution is done from "real dev" to Production, all Patches will be merged and you will get one solution in Production.
+== Related Content ==
+=== Microsoft Resources ===
 * [https://docs.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates Create patches to simplify solution updates]
-== Community Resources ==
+=== Community Resources ===
-* [https://benediktbergmann.eu/2021/02/28/how-to-handle-hotfixes-in-dataverse/ How to handle hotfixes in Dataverse]
+* [https://benediktbergmann.eu/2021/02/28/how-to-handle-hotfixes-in-dataverse/ How to handle hotfixes in Dataverse] by Benedikt Bergmann

@@ Line 5: / Line 5: @@
 Here follows an example:
 . Make sure it is the same version of the solution in "your new DEV" as in Production. If not, adjust version in "your new DEV".
 . Make a Clone of the solution in "your new dev". Under the Solution -> Clone -> Clone a Patch.
 . You will then get a new Solution and in that Solution you do the changes you want to do, which are meant to be the "fix for production".
 . Import the Patch to Production.
 . Make sure to do the same change in the "real DEV" environment. Either by doing it manually or by adding the components to an unmanaged solution in "your new DEV" and import to "real DEV".
 . The next time a deployment of the whole solution is done from "real dev" to Production, all Patches will be merged and you will get one solution in Production.

@@ Line 3: / Line 3: @@
 Imagine that you have your solution live in a production environment and you are about to start a new big project. During this project it might be the case that you need to do a smaller update/fix in the production environment, but you will not be able to do that from the DEV environment where you are working with your big new project. Because there will be changes you do not want to add to production yet. In the future you could potentially use Settings for this, but for now and an alternative approach is to make a copy of DEV to another environment before you start with your new project. In that temporarily DEV environment you could do the small fix and create a patch to import to the production environment.
-More to add here... We'll continue soon!
+Here follows an example:
 == Microsoft Resources ==

← Older revision		Revision as of 15:33, 21 December 2021
Line 7:		Line 7:
	== Microsoft Resources ==		== Microsoft Resources ==
	* [https://docs.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates Create patches to simplify solution updates]		* [https://docs.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates Create patches to simplify solution updates]
		+
		+	== Community Resources ==
		+	* [https://benediktbergmann.eu/2021/02/28/how-to-handle-hotfixes-in-dataverse/ How to handle hotfixes in Dataverse]

← Older revision		Revision as of 20:36, 17 December 2021
Line 4:		Line 4:

	More to add here... We'll continue soon!		More to add here... We'll continue soon!
		+
		+	== Microsoft Resources ==
		+	* [https://docs.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates Create patches to simplify solution updates]