Answered

Clone a Patch / Clone a solution

(1) Share

Report

Posted on by ctedesco3307

690

Hello - new to export / import for Power Apps. I have an existing solution in a dev environment. The solution consists of Apps flows and Dataverse tables. I need to make minor updates to one canvas app and change 2 flows. What's the correct way to import this to production? Should a Clone a Patch or Clone a solution? When I clone either one, they are empty -if I just add in what I changed (from the original solution) and Import into Production, will that work properly? Which option should I pick, clone a patch or clone a solution? Anything notable in the difference in those?

Thank you

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (7)

Answers (1)

Shashank Bhide 942 Moderator on at

Like (1)

Report

Clone a patch : creates a child solution of the main solution, the purpose is to only add things that needs to be changed and import them in the target. once a patch solution has been created, the main solution becomes immutable and can't be changed until the solution is cloned using 'clone solution'.

Clone solution : creates a new incremented version of the main solution by rolling up all the patches into the new version.

patching is good for short term, but eventually the solution needs to be merged, so if your solution is small and you're sure that nothing else has changed other than what your desired changes are, then, export the complete solution as managed and import it in your target.

Was this reply helpful? Yes No
ctedesco3307 690 on at

Like (1)

Report

@shashankbhide - thank you for responding - so you are saying clone a solution, add in just the 1 app and 2 flows I changed - then import that into Prod? Please confirm if you can.

Thank you

Was this reply helpful? Yes No
Shashank Bhide 942 Moderator on at

Like (1)

Report

I'm recommending don't clone (patch or solution) if your entire solution is small and you're sure that nothing else has changed other than your desired changes. Just export the full solution and import in the targe, however, if not, then use "clone a patch" to create a patch first.

Was this reply helpful? Yes No
ctedesco3307 690 on at

Like (1)

Report

@shashankbhide - this is the original solution in the dev environment. All I am doing is making minor changes to the one canvas app and 2 flows. Should I just export this entire same 1.0.0.0 version of the solution and import it to prod? - Thank you again

Thank youa

Was this reply helpful? Yes No
Shashank Bhide 942 Moderator on at

Like (1)

Report
Yes, technically nothing stops you from doing this, however, in future try to organize solutions in a better way.
Code (power automate and plugin) in one solution.
WebResource
Tables (and everything related to tables)
Security roles

Was this reply helpful? Yes No
ctedesco3307 690 on at

Like (1)

Report

@shashankbhide - I never thought of that! each separate 'asset' is it' own solution. That is excellent advice and makes total sense! I did not create this solution, but I have done mine in the past this way. I thought everything was supposed to be grouped together. Last question, if I just re-import the same 1.0.0.5 solution, no version increment will be present in prod - it will be the same as what was originally imported. Any issues to think about there? Appreciate you this morning - thanks again.

Was this reply helpful? Yes No
Verified answer

Shashank Bhide 942 Moderator on at

Like (2)

Report

Yes, importing under the same version number shouldn't be a problem technically, but again it's a good practice to increment the version before every import.

Was this reply helpful? Yes No