Best practices to manage PROD hot fix with Power Apps

(0) Share

Report

Posted on by Community Power Pla...

Hi guys,

I'm new to Power Apps and try to understand how we could manage PROD hot fix with Power Apps.

For example:

- I already published version 1.0 to PROD env

- Since then I'm working on sprint development features and have work in progress for feature A & B. They are both incomplete and still have issues

- Now I find out that v1.0 on PROD has critical bug that need immediate fix

What should I do in this instance to only push to PROD the fix for the bug but not bring incomplete feature A & B to PROD?

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (1)

Verified answer

Michael E. Gernaey 53,325 Super User 2025 Season 2 on at

Like (1)

Report

@ngmp96

You should create a Patch from whatever is the Code in Prod. Do it on another machine, doesnt matter, but load up the solution that is in Prod, somewhere. Create a Patch. Fix the issue in the Patch, deploy the patch. This assumes its part of a Solution learn.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates

if it's not part of a solution, then the only option you have is to load the App Version into a machine, fix it there, export and install it, however you do your normal process.

Its a little more of a pain without solutions and of course its Power Apps and I dont know if you mean canvas or model driven apps etc. Always look to provide too much information, versus too little.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @FLMike thanks for replying me. Can I ask more - initially I was just asking in general. But for canvas app vs model driven app - will the strategy be different or we should still use patch if we can?

Was this reply helpful? Yes No
Michael E. Gernaey 53,325 Super User 2025 Season 2 on at

Like (0)

Report

Hi @ngmp96

It truly depends, as it depends on if its a roll-up versus a hotfix(patch) etc. But I recommend you follow the same procedure, especially as you move to a DevOps pipeline (most will) in the future. It will make your life easier.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
Michael E. Gernaey 53,325 Super User 2025 Season 2 on at

Like (1)

Report

@ngmp96

If I have answered your question, I'd appreciate if you can mark it as such for me.

Cheers,
-Michael

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Thanks @FLMike

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

HI @FLMike would you mind clarifying how patch works for me?

For instance:
Given I have Test and Prod env
I have published version 1.0 to PROD and now having some code changes already added to Test since the release (would call it as 2.0).

Now I need to fix bug for version 1.0 on PROD.
Am I correct to follow below steps:
1. On Test, revert the version from 2.0 to 1.0 so that it's the same as PROD current version
2. Clone a patch for the main solution with version 1.0
3. Fix bug and test until complete
4. Publish the patch solution
5. Export the patch solution and bring it to PROD to re-import
6. Once complete fixing on PROD, go back to dev/test env to Clone the solution so that the main one and the patch are merged together

Please correct me if I'm wrong, but my questions are:
Q1. In step 5, after I import the patch to PROD -> will it automatically recognize the main solution in PROD and only merge the changes to that existing solution? Or there will be 2 separate solutions in PROD? If there're 2, do I need to do anything to merge them?
Q2. After step 6, How do I get the code I've added after v1.0 release (which is in version 2.0) back?

Was this reply helpful? Yes No