Looking for a way to organize my flows into different folders. i make flows for different departments in our company and it would make it much easier to work with folders of flows rather than one long list
Our recommendation is to use Solutions to organize your flows. We are also looking at if there are additional organizational capabilities that we can add to help you organize your flows.
+1 here. folders would be very nice to organise my flows into required groups.
Please stop suggesting folders! It's not the best way. Managed tags or metadata is the best way since one flow can belong to multiple processes... folders forces 1 flow to belong into a single folder.
Using the existing "Solutions" way to organize flows allow 1 flow to belong to multiple solutions.
This is really a must! I am using Flow a lot to automate part of my work. All my Flows for different lists, etc. are mixed up together. This is really basic, it becomes impossible to manage all my flows without the possibility to organise them by folders.
@chrisingh42188 , I kind of agree with @asdfaf4 - organizing solutions has a role here - but I agree that the built-in options do not scale well. Best I could think of, is to export my flows from different tenants, environments and solutions as HTML to a fixed location. I chose a repo folder in a SharePoint library, so the actions and descriptions are crawled. In a short video https://youtu.be/vDW7ebi2nx4 you can see how that would work. Hope it helps pending a more integrated functionality in that regard. Cheers, Marc
I looked into this now and seeing as this request has been open for years..... and that my flows are getting bigger and I just decided to design my own MS list.
I could customize everything about it add a hyperlink to the actual flow, upload documents, put in reference links. I have a subject and tags associated with it. Now I can filter it and play with the data as needed.
Just thought I would pop this in here to help anyone who may need a solution - (My list is also version controlled and backed up - and I attach a .zip for each flow into the list too - just incase I lose it or someone wants a copy to play with.)
Based on the low volume of updates on voted items, and the type of activity/engagement from the MS Team and the rare software feature update, it appears Power Automate team is made of a single intern. This platform as a ton of potential, but it appears Microsoft is no longer caring about it and implementing what we need... 😞
@Kizzie , are you programmatically attaching that Zip of the flow? There is an action to export the flow definition as json which I tried using as a means of "archiving" them. There is also an action to create a flow from a json file, but it doesn't actually work with the json that's produced by the export action.
Solutions do not necessarily solve the issue of just being able to sort or group Flows. At a minimum, make the list sortable by name. Only being able to sort by last modified date doesn't give a good user experience. That's a simple UI change that would take 1 line in jquery.Also, not everything needs to be in a Solution. Sometimes, you might have 2-3 Flows for a particular function but that doesn't really merit a Solution.
Plus, if Solutions are the recommendation, then fix the bugs with adding certain Flows to Solutions. I have probably a dozen or more than give cryptic errors when trying to add them.
I totally agree with @FatherJ. Any list should be sortable, filterable or searchable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.