Power Platform Build Tool - Solution Upgrade and Remove Solution Missing

[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

[Sugaprakash]

@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

[Shan-Mcarthur]

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.

[coreyobrien]

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

[Anonymous]

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.

[Shan-Mcarthur]

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

[Shan-Mcarthur]

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.