cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Merge Solutions automatically using devops pipelines or others apps

Hi everyone,

I'm running into the task to deploy the company application to multiple enviroments (qa and prod), we have a "complex" structure, what I can say is the next to give you the better undestanding.

We have multiples solutions and we have our main solution where all of us should put our changes, works like a git repository.
We have some components in other solutions, so... our applications is splited on 2 to 3 solutions, we don't want to export and import manually every single solutions because they could increase in the future.

Is there any way to add a list the solutions we want to merge and then merge into a single solution?

I've seen a video about how to make this possible using XRMToolbox but I'm not sure if we can automate this proccess using this tool

1 ACCEPTED SOLUTION

Accepted Solutions
parvezghumra
Most Valuable Professional
Most Valuable Professional

@RodrigoQuintana 

 

I assume the solutions you're looking to merge are all unmanaged?

 

Are you using Azure DevOps or GitHub Actions? If Azure DevOps, which extension are you using for your pipelines?

 

If Azure DevOps and you're using 'Power DevOps Tool' (https://marketplace.visualstudio.com/items?itemName=WaelHamze.xrm-ci-framework-build-tasks), you can use the Copy Solution Components task to copy components from one solution to another (ie. the merging you're describing). There might be something similar available in other extensions or even Microsoft's official Power Platform Build Tools extension (https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools), but I'm not 100% sure about this.

 

There's also the 'Add Solution Component' task available in Microsoft Power Platform Build Tools, but I think you would need to explicitly specify which component is to be added for each component. This may not work for your scenario. A similar action is also available in Power Platform GitHub Actions: https://github.com/microsoft/powerplatform-actions/tree/main/add-solution-component

 

If all else fails you could potentially write your own logic to perform the necessary merge logic using the available SDK, tools, APIs etc

 

 




Parvez Ghumra, XRM Solutions UK
Microsoft Business Applications MVP | Power Platform | Dynamics 365 CE/CRM | Azure - Developer | Technical Consultant | Technical Architect | Community Super User | User Group Co-Organizer | Blogger

If this response helped you in any way, please give kudos by clicking the 'Thumbs Up'/'Like' button and/or marking it as an 'Accepted Solution'. This helps others by providing a quick way to identify likely solutions to their issues.

Also, for more useful content, please free to add me as a friend on this forum, follow my blog, follow me on Twitter and connect with me on LinkedIn

View solution in original post

3 REPLIES 3
parvezghumra
Most Valuable Professional
Most Valuable Professional

@RodrigoQuintana 

 

I assume the solutions you're looking to merge are all unmanaged?

 

Are you using Azure DevOps or GitHub Actions? If Azure DevOps, which extension are you using for your pipelines?

 

If Azure DevOps and you're using 'Power DevOps Tool' (https://marketplace.visualstudio.com/items?itemName=WaelHamze.xrm-ci-framework-build-tasks), you can use the Copy Solution Components task to copy components from one solution to another (ie. the merging you're describing). There might be something similar available in other extensions or even Microsoft's official Power Platform Build Tools extension (https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools), but I'm not 100% sure about this.

 

There's also the 'Add Solution Component' task available in Microsoft Power Platform Build Tools, but I think you would need to explicitly specify which component is to be added for each component. This may not work for your scenario. A similar action is also available in Power Platform GitHub Actions: https://github.com/microsoft/powerplatform-actions/tree/main/add-solution-component

 

If all else fails you could potentially write your own logic to perform the necessary merge logic using the available SDK, tools, APIs etc

 

 




Parvez Ghumra, XRM Solutions UK
Microsoft Business Applications MVP | Power Platform | Dynamics 365 CE/CRM | Azure - Developer | Technical Consultant | Technical Architect | Community Super User | User Group Co-Organizer | Blogger

If this response helped you in any way, please give kudos by clicking the 'Thumbs Up'/'Like' button and/or marking it as an 'Accepted Solution'. This helps others by providing a quick way to identify likely solutions to their issues.

Also, for more useful content, please free to add me as a friend on this forum, follow my blog, follow me on Twitter and connect with me on LinkedIn

Hi , can you share some docs on writing the merge scripts  the requirement is  the below ,

 

multiple devs would would be working on different components in separate solutions, all their solutions should me merged to main solutions along with components , we want to achieve and implement  this through ci cd Pipeline (azure devops) , 

can you please let us know what would be the ideal approach here , 

parvezghumra
Most Valuable Professional
Most Valuable Professional

@Sanjay_Ramaling 

I would suggest the following approach:

1. Establish, agree and document which are your "main" solutions

2. Install 'Power DevOps Tools' extension into your Azure DevOps extension from here: https://marketplace.visualstudio.com/items?itemName=WaelHamze.xrm-ci-framework-build-tasks. You will need admin privileges for this

3. Create a pipeline in Azure DevOps that will be manually triggered and have 2 input parameters to be set manually: first is the unique name of the source solution, and the second is the unique name of the target solution. If you're intended for only 1 main solution, then the target parameter can be omitted from manual setting and can be set using environment variables/hard-coded instead.

4. The pipeline will 2 tasks: first the 'Power DevOps Tools Installer' and then the 'Copy Solution Components' task to copy components from the source solution to the target solution

5. Optionally you can have a third task to delete the source solution

6. Ideally at the end of this you would want additional tasks to:

a) Increment the solution version number

b) Publish all customisations

c) Export the unmanaged and managed solutions, unpack them and commit them to source control

 

You will need ensure there is good communication between team members to ensure that no component is included in more than one developer solution and no changes are made directly in the main solutions




Parvez Ghumra, XRM Solutions UK
Microsoft Business Applications MVP | Power Platform | Dynamics 365 CE/CRM | Azure - Developer | Technical Consultant | Technical Architect | Community Super User | User Group Co-Organizer | Blogger

If this response helped you in any way, please give kudos by clicking the 'Thumbs Up'/'Like' button and/or marking it as an 'Accepted Solution'. This helps others by providing a quick way to identify likely solutions to their issues.

Also, for more useful content, please free to add me as a friend on this forum, follow my blog, follow me on Twitter and connect with me on LinkedIn

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,829)