Power Platform Build Tool - Solution Upgrade and Remove Solution Missing

(0) Share

Report

Posted on by Sugaprakash

Hi,

Solution Upgrade and Remove Solution components are missing in power platform tools.

Do we have any idea when we get this feature released?

Thanks

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (15)

Answers (1)

Shan-Mcarthur on at

Like (0)

Report
Copy link

Link copied!

We recommend using your source control as the master source of truth. When you have a deployment with an issue, simply create a branch in your source code to support the production deployment, fix the issue, generate a new version and deploy it. Then merge that branch back to your main development. Alternatively, if you want to roll back everything, simply change the version number on your old solution to one higher and deploy it. Both approaches are 'rolling forward' with a fix. There is no real support of rollbacks in the solution system. We maintain our own applications using these strategies too.

Was this reply helpful? Yes No
Shan-Mcarthur on at

Like (0)

Report
Copy link

Link copied!

The upgrade pattern was added to the build tools (all of them).

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

Like (0)

Report
Copy link

Link copied!

I understand it introduces complexity in managing source control if we are following the patches approach.
But how do we rollback the changes from production if we go with the upgrade deployment approach.
When we upgrade the solution, there is a just single layer for the solution. What if we want to restore the previous version of the solution if something goes wrong?
And also is there any way to deploy the components partially without deploying the entire solution which may introduce bugs in production.

Was this reply helpful? Yes No
cobr16 4 on at

Like (1)

Report
Copy link

Link copied!

@Shan-Mcarthur any chance the "Upgrade Solution" option is being added to the Power Platform Build Tools (maybe as an option on Import Solution)?

Was this reply helpful? Yes No
Shan-Mcarthur on at

Like (0)

Report
Copy link

Link copied!

We are not planning on removing patches, but their use in the future will be much lower once the other improvements I am talking about are done. I don't want folks to jump to the conclusion that we are removing something. I want them to understand that we are investing in ways to make standard solution actions simple and effective without customers needing to jump into really complex things like patching. You will be able to achieve the same things that drive you today to use patching by using a standard solution in the future without needing to use patching. This is NOT saying that we are deprecating patching.

Was this reply helpful? Yes No
Sugaprakash 15 on at

Like (0)

Report
Copy link

Link copied!

@Shan-Mcarthur

Thanks for your response.

As per your suggestion, if we use whole or base solution for deployment instead of patch, I dont see the scenario to use patch.

As most of the customers wants to implement Devops for power platform projects, Will Microsoft remove patch concept in feature release?

Thanks,
Suga

Was this reply helpful? Yes No
Shan-Mcarthur on at

Like (0)

Report
Copy link

Link copied!

I highly discourage the use of patches, especially for customers that are source-code-centric and using DevOps tooling. It adds way more complexity than it adds in value. Solution import performance is improving significantly to the point where solution update performance will match a patch. We will also then be considering adding delete actions on to the update pattern, eliminating most of the reasons why you would need to use patches or the stage-for-upgrade pattern. In the meantime, the other answers about patches not doing deletes is accurate. The only 2 solution actions that can invoke a delete is the removal of the solution (which will delete ALL components and data in the solution) and the promote-and-delete leg of the upgrade pattern. All other solution actions are additive.

Was this reply helpful? Yes No
Sugaprakash 15 on at

Like (1)

Report
Copy link

Link copied!

@mtoma Thanks for your comments.

I too agree, Patch will not delete the components.

I think, The scenario to delete the components in higher environment will be very less.
If such delete scenario occurs, I have separate pipeline for solution upgrade which will take care of removing/deleting the components from solutions.

If we are not following patch concepts, we have to deploy all the components every time which will have high risk of introducing new bugs in the system.

And also In Power automation deployment, I may end up updating the connections and turn on them every time which is very time consuming manual process and high risk of introducing bugs.

If i use patch which will not affect the existing unchanged power automation flows where the manual process will not take much effort and low risk.

Thanks,
Suga

Was this reply helpful? Yes No
mtoma on at

Like (0)

Report
Copy link

Link copied!

hi @Sugaprakash ,

Thank you for the response.

There is a small problem with patches, they are unable to delete components, and also you have components performing merge, like Forms, Optionset values, Sitemaps and App Modules, if I'm not mistaking.

Given the fact that you do not seem to have any of those components performing merge in your solution, you might be ok with this clone a patch approach.

If you are ok with this limitation, yes you can try this approach, otherwise I will recommend you to try to go to the interface and perform the upgrade for now.

Was this reply helpful? Yes No
Sugaprakash 15 on at

Like (0)

Report
Copy link

Link copied!

@Shan-Mcarthur @mtoma

Thanks for quick response.

I have attached the power automation devops pipeline approach. Please review and suggest me if i have to correct anything in the deployment process.

Approach:

1. Create base solutions (segmented) for initial development.
- DataModel, SecurityRole, Workflows, PowerAutomation, CanvasApps, Other
2. Create Patch solution for each sprint and deploy in Test through pipeline.
3. Deploy patch solutions from repository to UAT through separate pipeline.
4. Deploy patch solutions from repository to Prod through separate pipeline.
5. Apply Solution upgrade through pipeline.

PowerPlatform_Dep...

Was this reply helpful? Yes No