Hi all,
Here is my use case:
What would be the best practice to make a "hot fix" to the app on the DEV environment (in its PROD version) and deploy it on the PROD environment without transporting the newest app improvements (which will be deployed on PROD in the coming weeks)?
Hi there @R3dKap
I actually did just that earlier today. Don't know if it is the "best practice" but it sure worked.
Having saved all the improvements, you can just go to the Power App versions list and:
Be aware to write down what is your "DEV" version so that you can publish it again after you deploy your solution to PRODUCTION, and of course, don't forget to solve the bug as well in the "DEV version".
Don't forget to click "Accept as answer" if this reply pleases you 😉
Hi @Feiteira,
Thanks for your reply... Yes I thought of that solution but I didn't find it very elegant. Furthermore, I have other artefacts in my solution which I don't want to deploy in their new version on PROD. So I thought of creating a new solution with just the canvas app, restore the app to the PROD version, fix the bug, export the solution and deploy it to PROD. But then I would have two solutions on PROD for the same canvas app... Not ideal...
I was thinking of using the patch procedure (https://learn.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates) but this sentence is not very reassuring:
So I'm waiting for anyone who has experienced it or has another solution... 🙂
User | Count |
---|---|
254 | |
106 | |
84 | |
51 | |
43 |