cancel
Showing results for 
Search instead for 
Did you mean: 

Provide a method of organising Flows

Working with flows is very messy if you are working on a batch of flows that contribute to one task.  A system of being able to tag flows or put them in folders would allow you to work more seamlessly on specific flow groups.

Status: Completed

You can now organize your flows into solutions. Solutions are like tags or folders. They are like folders in that they can contain flows, plus they can contain other assets like PowerApps, CDS entities etc.... They are also like tags in that a single flow can be in more than one solution - so your not tied to one strict heirarchy. The new Solutions tab is available for any envirnomnet that has CDS enabled. Read more here: https://flow.microsoft.com/blog/solutions-in-microsoft-flow/

Comments
Level: Powered On

@spg-john-liu, I wasn't aware that API paging would be an issue for sorting Flows by name on the admin page; I looked into Flow Studio awhile ago but never really had the time to properly check it out. I'll revisit it, thanks for the tips.

Level: Powered On

Anyone else have concerns giving access to your account to a third party? Flow Studio does look cool, but has anyone audited what they do once they are given access to your account? I have an admin account for our O365 tenant. 

Level 8

Hey @grovercorner2 


Updated I put the answers into an FAQ page
https://flowstudio.app/welcome/about/security 

 

As for best Flow security setup - I would create Flow environment admins and have them own P2 license and create environments for production Flows to live in.  A Flow environment admin shouldn't be a tenant administrator - so Flow Studio will borrow that environment admin's P2 license to scan all the environments.

 

That'd be how I do this.

 

 

Level: Powered On

@grovercorner2 we have used FlowStudio on this tenant for over a year without issues and zero red flags

Level: Powered On

I'm confused as to why this is marked as completed. I can't use this new Solutions "solution" on any of my flows involving SharePoint, and it appears this was intended behavior.

 

When I went to add an existing flow to a Solution, I couldn't find basically any of my Flows and then found a link that says "Some flows are currently not available to add to solutions. Learn more" with "learn more" being a clickable link.

 

The link goes here: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/use-solution-explorer#known-lim...

 

One of the items on that page is this: "Flows that connect to SharePoint are not available in solutions."

 

So, this does me no good at all. It's like all I wanted was a pocket knife and I got handed a 21-tool Leatherman multitool that doesn't do what I need.