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

[mtoma]

Hi @Sugaprakash ,

Thank you for this post.

The option of removing a solution component is already available, it has been there for at least a couple of weeks, please find it in attachment.

Regarding the solution upgrade, we are currently redesigning the process, therefore I would advise you to wait for the redesign and see if that process is still required after this.

Thank you for using Microsoft Dynamics 365 Communities,

Madalina Toma
Support Engineer
Microsoft Dynamics 365

[Sugaprakash]

@mtoma I was asking about power platform build tools components for devops implementations.

I don't see  components to implement rollback and solution upgrade components. Please find the attached screen shots for reference.

[mtoma]

Hi @Sugaprakash ,

Let me ask the feature owner if they have the two features planned.

Thank you!

[Sugaprakash]

@mtoma ,

Thanks for your response.

I have build the pipeline as per screen shot below.

Here My solution name "IROC_MBE_BASE". but when unpack and check in the solutions in github, i am seeing new folder as "Others".

Do you have any idea why other folder is getting added in github.

[Shan-Mcarthur · Accepted solution]

The 'other' folder contains some of the high level files from the solution file including the solution.xml and customization.xml file.  Open up the folder and you will see the contents.  This is standard behavior of the Solution Packager tool as it breaks apart the monolithic solution zip file into source control-ready artifacts.

[Sugaprakash]

@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.

[mtoma]

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.

[Sugaprakash]

@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

[Shan-Mcarthur]

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.