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

Copy/Duplicate a Flow in a Solution

I have a Flow in an existing solution for which I need to create several variants. Ideally I would copy the flow and edit the copy. 

Unfortunately the copies are created outside the solution and are not visible to import into the solution.

Any ideas on how to replicate a Flow inside of a Solution?

 

Thanks,

 

Brian

2 ACCEPTED SOLUTIONS

Accepted Solutions
abm
Most Valuable Professional
Most Valuable Professional

Hi @bhitchlockfcs 

 

Yes you can but only way is to edit the xml files.

 

Follows the below steps:

 

Note: Before you do this take a backup copy of your existing solution.

 

1. Export the current solution

2. Once the solution is exported then unzip the current solution

3. You will see the following files and directory

     image.png

 

4. Go to Workflows directory. Here you can see the flow json file.

 

5. Duplicate the flow file and rename to another filename and new GUID. To generate new GUID use this site https://www.guidgenerator.com/online-guid-generator.aspx

 

6. Once the file is copied and renamed with new GUID you will have two json flow files like below. Makes sure GUID must be capital case.

 

image.png

7. Next go to back to parent folder and open customizations.xml file

 

8. Copy and paste (duplicate) the workflow element. See below. Here the highlighted part is the first flow you created. Below you can see my new workflow node I copied.  change the GUID's workflowID (Use the GUID you generated), Name and JsonFilename. Please be careful that all are case sensitive. So follow the same pattern as the first workflow where you copied form.

 

image.png

Save the file.

 

9. Next open the Solution.xml file

Duplicate the Root Component. Again the id is case sensitive. Use the same flow GUID as above.

 

image.png

 

   Save the file

 

10. Finally Zip all the files.

 

12. Delete your existing solution. (Please take a backup copy of your solution).

13. Import the new zip solution.

 

Here is my result

image.png

If you need any help in this please let me know.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

View solution in original post

Welbywelb
Advocate III
Advocate III

Sorry I know this is old but it might help someone.

Actually you can do it with Postman. Create a Skeleton destination flow (just through away steps in it) and save it.

In Chrome open the inspect window and navigate to the "network" tab and capture the PATCH post URL (we will use this in Postman) and Bearer token.

Go to the flow you want to copy and in Chrome open the inspect window and navigate to the "network" tab. Click the "Save" on it and capture the body of the Patch command (Request Payload - starts "properties:..). 

Got to Postman and create a new Patch request (copying your Bearer token to the authentication) and past the body of the flow you want to copy. Lastly edit the "displayName" so it matches what you called the Skeleton flow.

Hit Post and the Flow should be be updated with the contents of the one you just copied.

 

Really ugly way of doing but its probably quicker than exporting the entire solution and updating it.

 

You might need to watch out for the only "16 connection limit" on one reference issue - if you get this open the Skeleton app and connect to CDS and create a new connection save it as before and examine the properties payload you will see the mentioned connection has changed name - copy this to the same field in the payload you want to test and you should be up and running. 

View solution in original post

39 REPLIES 39
abm
Most Valuable Professional
Most Valuable Professional

Hi @bhitchlockfcs 

 

Yes you can but only way is to edit the xml files.

 

Follows the below steps:

 

Note: Before you do this take a backup copy of your existing solution.

 

1. Export the current solution

2. Once the solution is exported then unzip the current solution

3. You will see the following files and directory

     image.png

 

4. Go to Workflows directory. Here you can see the flow json file.

 

5. Duplicate the flow file and rename to another filename and new GUID. To generate new GUID use this site https://www.guidgenerator.com/online-guid-generator.aspx

 

6. Once the file is copied and renamed with new GUID you will have two json flow files like below. Makes sure GUID must be capital case.

 

image.png

7. Next go to back to parent folder and open customizations.xml file

 

8. Copy and paste (duplicate) the workflow element. See below. Here the highlighted part is the first flow you created. Below you can see my new workflow node I copied.  change the GUID's workflowID (Use the GUID you generated), Name and JsonFilename. Please be careful that all are case sensitive. So follow the same pattern as the first workflow where you copied form.

 

image.png

Save the file.

 

9. Next open the Solution.xml file

Duplicate the Root Component. Again the id is case sensitive. Use the same flow GUID as above.

 

image.png

 

   Save the file

 

10. Finally Zip all the files.

 

12. Delete your existing solution. (Please take a backup copy of your solution).

13. Import the new zip solution.

 

Here is my result

image.png

If you need any help in this please let me know.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Jcook
Most Valuable Professional
Most Valuable Professional

@abm that is a great post.. definitely saving this for later.

—Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





abm
Most Valuable Professional
Most Valuable Professional

Hi @Jcook 

 

Thanks for the comment. Really appreciated it. Keep up the good work. I can see you doing well in this community sharing your knowledge.

 

 



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Jcook
Most Valuable Professional
Most Valuable Professional

@abm thanks, I enjoy helping where I can. Also I have found that I learn so much more when helping others.

So it’s a win win.

—Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





Thanks @abm,

 

I was afraid that would be the answer. These Flows are part of a larger Model Driven App solution. So editing and replacing the solution is a little more involved. Does the content of the solution or whether it is managed/unmanaged make a difference to your workaround?

Thank you for the detailed directions.

 

Brian

abm
Most Valuable Professional
Most Valuable Professional

Hi @bhitchlockfcs 

 

I haven't checked the managed solution to extract and reconstruct the solution. It may be possible. Not sure that is supported or not?

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
FIN
New Member

@bhitchlockfcs 

Also you can go to your flow click save as (a new copy will appear in "My flows") and add new flow to your solution.

 


@FIN wrote:

@bhitchlockfcs 

Also you can go to your flow click save as (a new copy will appear in "My flows") and add new flow to your solution.

 

You would think it would be this easy.  It would save a lot of time for larger projects.  The copies are not available to me either when attempting to add them to my solution.


 

Now I see why I had this problem. So there is a list of known limitations (for example Button triggered flows are not available in solutions). So if you want to copy and import a flow you'll need to switch trigger (or anything else on the list) to be able to import it.

See:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/solutions-overview#known-limita...

 

So i created a solution and 2 flows:

FIN_1-1606929725271.png

Saved the copy:

FIN_2-1606929780826.png

 

And on add existing flows I see only Copy of - TestSaveAs - OneDrive

FIN_3-1606929841547.png

And i can add it.

 

So to be able to import existing flow you'll need to change/delete some steps.

dialedin
Advocate II
Advocate II

Ah, good find.

 

In my case, I created the copy from a flow already in the Solution, so it didn't have any unsupported limitiations.

Welbywelb
Advocate III
Advocate III

Sorry I know this is old but it might help someone.

Actually you can do it with Postman. Create a Skeleton destination flow (just through away steps in it) and save it.

In Chrome open the inspect window and navigate to the "network" tab and capture the PATCH post URL (we will use this in Postman) and Bearer token.

Go to the flow you want to copy and in Chrome open the inspect window and navigate to the "network" tab. Click the "Save" on it and capture the body of the Patch command (Request Payload - starts "properties:..). 

Got to Postman and create a new Patch request (copying your Bearer token to the authentication) and past the body of the flow you want to copy. Lastly edit the "displayName" so it matches what you called the Skeleton flow.

Hit Post and the Flow should be be updated with the contents of the one you just copied.

 

Really ugly way of doing but its probably quicker than exporting the entire solution and updating it.

 

You might need to watch out for the only "16 connection limit" on one reference issue - if you get this open the Skeleton app and connect to CDS and create a new connection save it as before and examine the properties payload you will see the mentioned connection has changed name - copy this to the same field in the payload you want to test and you should be up and running. 

Wow, this s/b the actual solution. Well done.

Jcook
Most Valuable Professional
Most Valuable Professional

Awesome post @Welbywelb !


Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





Thanks Welbywelb!

 

Your solution worked great!  Where you stated, "Click the "Save" on it and capture the body of the Patch command (Request Payload - starts "properties:..).", when I saved the file from Chrome Dev Tools, the double quotes were escaped by backslashes, that I had to remove (a simple find and replace).

 

In file saved from Chrome:   

"text""{\"properties\":{\"definition\":{\"$schema\":...
 
In postman, placed in the Body - Raw section,  I put:
{"properties":{"definition":{"$schema":...

thx @Welbywelb for the fantastic workaround. I've added some more details including screenshots 🙂 The post is in german but this should be no problem. Klonen bzw. Kopieren von Power Automate Flows innerhalb von Solutions | applied technologies GmbH

Your article explains @Welbywelb solution in details! Precious! Thank you both!

   

The solution I found without exporting/reimporting the solution is to use "save-as" for the flow you're interested in. Then importing the new exported flow back into the solution. I'm always weary of deleting my solution and trying to reimport especially if it's a critical flow. I have seen odd issues over time and don't trust the solution import too much.

Has anyone tried this workaround and what has been your experience? 

 

I really wish Microsoft would fix the "Save-As" and the "Clone" features so we can safely work/test our work. The "save-as" should just save the flow inside your solution if the flow is already inside, and not outside. 

The "Clone" solution should clone the entire solution including flows and connection references (I read this article and made me scared to even try that feature: Solved: Clone Solution issue - Power Platform Community (microsoft.com) See also this for more info: Power Platform – Clone Solution | innovativeaj (wordpress.com)

Maybe MSFT will fix this in future releases. Hope MSFT is reading this blog 🙂 

 

Welbywelb
Advocate III
Advocate III

Hi Maxpower4522,

 

Very interested in this so I just tried to do a "save as" from within flow in a solution and the flow is placed in "My flows".  If I try to "Add existing" ..."Cloud flow"-> "From Dataverse or Outside Dataverser" then the flow is not visible (I've assumed this is what you mean when you say "importing the new exported flow back into the solution") but perhaps there is another way to do it from inside a solution. FYI this was a "manually triggered flow" so this might be the issue.

 

Can you share the navigation steps you do which successfully imported a previously "save as"'d flow please if different from above?

Also what kind of flow trigger is used with within it?

 

FYI it appears that there are many reason for this not to work see - https://docs.microsoft.com/en-gb/powerapps/maker/data-platform/solutions-overview#known-limitations

 

This is the reason I provided my solution above which basically allows you cut and paste the code content for a any flow into a skeleton flow which you have created where you want it (inside a solution or not).

I totally agree that we shouldn't have to do this but until MS gets the finger out its the best solution I've found to date.

 

Thanks.

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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 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 SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     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 Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

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.    

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 (4,507)