Currently, we cannot sort nor organize flows in any way I could find. It makes flows very difficult to manage.Thank you.
The idea of having a way of organizing flows has already been submitted and closed as "completed" (read link: https://powerusers.microsoft.com/t5/Flow-Ideas/Provide-a-method-of-organising-Flows/idc-p/281582#M14...
Unfortunately, the solution provided does not seem to answer the community needs, therefore I am reopening it again.Tagging here users who commented recently on the first link, please vote: @ksteelbaron , @asdfaf4 , @grovercorner2 , @ctyst , @OlafStetzer , @JoshMohr , @Murderbot , @rjhale
Thanks for reopening this. I completely agree that they shouldn't have closed the previous idea given the state of things. Hopefully we'll see some quick upvoting on this one.
Agree, the previous one should not have been close. They haven't done anything yet.
I dream of this every day. Currently my only method of "organizing" flows is by sharing them with my test account!
Agreed! Thanks for reopening this issue. Even a basic name sort would be better than what we have now, which is NOTHING. It cannot possibly be that hard to add a column sort function.
Wish there was a way to at least group the flows by what List/Library in Sharepoint or other Application. I have one list in SharePoint that has 10 FLows associated with it. Would be nice to group them together like you can group List and Library items in SP
Agree, the Solution method is not enought for all scenarios. We do not use Common Data Service as Data Source and the Solution method requires to have it enabled. A basic solution to create Folder to manage flows or group them based on an created Application will be useful.
This is a must have so that we don't have scroll through them. Please help asap, and please don't mention the "Solution" option for CDS, we're not using that.
At a bare minimum, let the flow list be sortable, filterable and searchable, this way, we can have a cheap "naming" convention until we get manageable "tags" and be able to group by those tags. With tagas, a workflow should be able to able to be visible in multiple logical groups.
I have hundreds of workflows that I created and I'm now making mistakes due to the fact that I can't logically group them together around a logical departmental process.
maybe adding a tag, so we can tag a flow, or shared flow, in a way that is meaningful for us to group?
In addition to adding additional relevant columns in the Flow list views, I'd like to see filtering and sorting on all the columns.