Turn a facetted search into a View using the facets on the Filter tab

I don't think this is currently possible unfortunately. Note also that views are solely based on object metadata, so if your search included any quick search terms that targeted the file contents, these would be dropped when creating a view based on the search.

We are currently thinking of ways to make the view creation easier and more intuitive in general, these enhancements start rolling out next year.

Thanks Joonas,

We believe this would be very useful for the users that work with M-Files if this could be added to the standard product.

How do we proceed with this, will you raise an Enhancement Request or similar?

Sure, I can do that. How would you envision this working? If a user has for instance searched for "invoice" and selected facets "2023" and "ACME Inc.", and you save these facets as a view, what should the view display? Can you give some examples of facets you are often using and would like to save as view?

I see the view creation from facets being based on the defined facets only. E.g in your example, if Invoice was a class and Class, Company and Year were facets, then the user would select the following in the Filter tab:
In the Class facet: Invoice
In the "Company" facet: ACME Inc.
In the Year facet: 2023
So instead of the user repeatedly filtering for Invoice, ACME Inc and 2023, s/he could save this as View

I was thinking more that "invoice" would be the search term typed into the search bar. Would it be clear to the user that this search term would be dropped from the created view, since views cannot include such quick search terms? In other words, the items they would see in the new view would not match what they got in the search results, since the search conditions are different.

If a user would try to create a view where search terms are included, for a good user experience I think there should be a warning that search terms would be dropped, and an option to Cancel or to continue to create the view.

Thanks, I've created the feature request with ID 169206. Our product team will do further discovery if they decide to take this idea forward.

Thanks Joonas!