Add existing flows to Solutions

[Anonymous]

Hi,

Under the 'Solutions' feature there is a button called 'Add Existing' yet no items appear there.

How can I add existing flows in my environment to a new solution? 

Sam

[v-yamao-msft]

Hi @Anonymous ，

Do you want to add an existing flow to Solutions?

Have you followed the steps suggested in this blog:

https://flow.microsoft.com/en-us/blog/solutions-in-microsoft-flow/

I have just made a test on my side, existing flows could be selected for new Solutions:

Please take another try with it.

Best regards,

Mabel

[Anonymous]

Hi,

Those are the exact steps I have followed and yet the window is still blank and I can't choose any flows

Sam

[NielsL]

@Anonymous,

Did you find a solution to your problem? I'm as well not able to add existing flows to my solution.

[Piper]

@v-yamao-msft I'm in the same boat here as well. I can only see Flows that already exist in a a solution. If it is a Flow that I created in My Flows I can't add it to a solution.

[Anonymous]

@NielsL Nope, still blank for all environments.

[NielsL]

@Anonymous,

Thanks for the feedback. I hope they solve this. I would rather not have to re-create 20+ flows from scratch  

[DavidYack · Accepted solution]

Support for Add Existing, of flows that were created outside of solutions is on the April 19' feature list currently targted to June - https://docs.microsoft.com/en-us/business-applications-release-notes/april19/microsoft-powerapps/imp...

[Piper]

Thanks @DavidYack! I'm so glad to see that feature added. Sometimes it's like Christmas reading those release notes

[rlogan]

I want to bump this thread.  It appears this is still not working, at least in my environment.

When trying to add 'outside flows', no components are brought back for selection.

Does anyone have this working?  Most of my components are scheduled, or automatically tiggered through CDS and D365 connectors.

[ChuckO]

Yep same symptom for my environment.  I have flows sitting in My Flows, but want to now consolidate and export as a solution and can't seem to be able to select them for inclusion in a newly created solution.

[rlogan]

This issue is now resolved.  I submitted a support ticket for this, and was forwarded along to the product team.

[NielsL]

Yeah, it is possible now. However, I think I'll wait a while before including my flows in a solution. 

From this thread on crmug.com people are reporting, that you have to manually have to re-create the connections for every flow when you move the solution from one environment to another. For some connectors, e.g. not directly elated to CDS, you might need to do that. However, using the CDS connector and selecting the 'current environment' this shouldn't be necessary - but it is.  

[Chaowang]

Hi, 

I still have the same problem, within a solution, I don't see the any existing flow to add.

Thanks

[rlogan]

@NielsL   Yes, when importing the solution, it does not allow you to select which Connector to use unfortunately.  However, I noticed if you do a Save As, there is an option to select the Connector there.  It does apply to connector to all actions.  Unfortunately this is not an ideal solution since you're duplicating all of your Flows.

[rlogan]

@Chaowang The only Flow I was not able to add to a solution, was an instant triggered flow.  I had to recreate that manually in the solution. 

Can you provide a screenshot of what you're trying to add?

[Chaowang]

Hi @rlogan ,  Of course,  I have several flow created when develop the application, but in a solution, i can add the existing canvas app, but i can't add exsting flows. 
Because  i need to do deployment automatized with the solution for another environment, if inside the solution no include the flow, the deployment just deploy the app without flows.

[rlogan]

Hi @Chaowang ,  It looks like this is a known limitation.  Canvas app triggered flows cannot be added to solutions.  See the following link:  https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/use-solution-explorer#known-lim...

[Kumbol]

Same limitation applies to any Flows that connect to SharePoint or other M365 services... which basically eliminates all of my Flows. 😞 It's a bit surprising, given how 1st party integrations were alwyas a key benefit of using Flow.

[rjhale]

I'm confused.  Stephen from the Flow team mentions in the comments section of this page that "Today all SharePoint triggers/actions are fully supported, with the exception of triggering from the button in the menu for a selected item".  That statement makes it sound like I should be able to add Flows with SharePoint connections to a Solution.  

FWIW, I've tested this on my end, and I'm still unable to add any of my SharePoint related Flows to a Solution.