Power Platform Solution Patching and Cloning Tutorial

preview_player
Показать описание
Learn how to deploy pieces of your complete solution from environment to environment by patching and cloning the solution. You can use this technique to withhold a change that's not ready for production but still deploy an important urgent fix.

🎥 Power Apps Solutions Video:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - -

Next step on your journey:

Let's connect:

Pragmatic Works
7175 Hwy 17, Suite 2 Fleming Island, FL 32003
Phone: (904) 413-1911

-~-~~-~~~-~~-~-
Please watch: "(275) Free Pragmatic Works Power Apps Component Library "
-~-~~-~~~-~~-~-
Рекомендации по теме
Комментарии
Автор

Great Video, thank you <3 is there a solution to solution(sorry) export-import for solutions created by third persons? Is it possible do deploy them without enabling "managed environments" from dev to test to prod environments?

budzugan
Автор

Thanks, can you clarify this please
6:12 - After bringing the 1st patch to PROD I can see 2 separate solutions on PROD. So how do we make sure that end users will use version of the patch one rather than the original one?

phuongnguyenmai
Автор

Why wouldnt I just make that change in the unmanaged solution and perform an upgrade or update in the production environment? Wouldnt that accomplish the same thing?

thechristianinitiative
Автор

How do you revert back to the solution before the change?

timshinkle
Автор

Fantastic Brian - I've been looking for a patching solution for some time now. However, my company insists on us using Azure DevOps pipelines for building and deploying the solution, so am worried any patches done this way would interfere and cause problematic missing history in those pipelines. Do you have any advice regarding using DevOps alongside your method or as an alternative way? I've looked, but can't find anything so far.

stuartharrod
Автор

thanks Bran.. one query I have. Let say I do multiple patches. so in destination environment all will exists separately ? does it look good or we need always do a Clone solution (in source) and upgrade the destination so that there would only 1 solution ?

pradipta
Автор

can you add and import enviornment variables to patched solutions?

reivaxmik
Автор

We should "clone the solution" (merge the patch) in development or in the production?

legendgod
Автор

Let's say I have canvas app inside my solution, and I am adding a new screen, a feature which is taking some time. Then I need to make an emergency patch. That emergency is just changing a label on a different screen in the app. I would patch the app in dev, then in the patch, delete the screen that has the half built feature in it. After exporting to production I later patch the solution to get the new half completed screen back? How does it know which version of the app to use in the merged solution? I would want to keep the label change in the patch, and the new screen feature that is not in the patch.

fredbarnes
Автор

Hi!
Is it possible to convert a Managed solution to an UnManaged in my environment?

loveandhate