The first frustration for me is that as the architect of my system, it is not possible to restrict the fields that other users can select in personal filter. there are certain fields that I have which are helper fields, for example one that detects duplicates. this means that when users are applying a filter them must scroll through irrelevant fields to find the fields that they need. It makes me very very hesitant to create too many relationship fields or helper fields.
I would like to choose which fields are available for other users to apply as a personal filter.
The next request is that it be possible to have commonly used filters pinned to the top of the view, this is possible in Fibery but the button only turns the pinned filter on or off. In air table, I can a pin a field filter to the top of the view, that when a user clicks on it, they can directly input the values they are wanting to filter by.
I was just think about this a few days ago—I agree that this would be so powerful and help massively with usability. We have a lot of fields that general users don’t need to see. Being able to pin filters that can be changed via a dropdown would be a gamechanger.
Hi Bronn, great to hear this could be a good feature, I agree it would change the experience massively, fingers crossed that others agree and upvote!
Tom
Hi Renato, I’ve had a quick read of your post, I thought perhaps you could share some screenshots and description of the notion functionality that you like? And that might give the Fibery team some inspiration.
Also would really love to see this implemented. The current implementation of pinned filters as a button is really frustrating. Right now the only option for quick filtering a table is to use buttons like this. But if you want two independent filters targeting a dropdown, you have to create two buttons. When a new user opens the table, both buttons are active by default and the table appears completely empty as the filters overlap each other if you are using AND logic targeting a dropdown
The ability to have dropdown filters like this would completely solve this issue/constraint
For example a single select. Allow users to select from this pinned filter which single select to filter for. Not just on and off. (Yes its kind of like my filters, but just pinned and easier to use by members.
So if I am not an admin, all filters are only being edited for me? But if i am an admin, its being edited for everyone? So now admins no longer have “My Filters” option? Maybe adding something similar to Notion just for admins: “Save for Everyone”? Then admins can use filters as they need, play around with the data, without affecting it for everyone.
“Any person can enable quick filters” all users can enable and also disable? Not only admins and creators?
How will it work if an editor adds, removes, or turns into group, and then the admin makes a change to the quick filters? Will it get synced? Or once a user edits, it becomes out of sync with admin changes?
Some thoughts:
I think it’s putting too much functionality into one button, making things complex for editors. Why not allow quick filters to be either “Toggle” or “Dropdown”? Then some might be an On/Off button (as currently), while others are like Airtable, where on click, it directly opens the dropdown for filters. The designs need three clicks just to adjust the filters: 1. Click the arrow, 2. Click the drop down, 3. Select the one you want. In Airtable it’s just 2 clicks.
When making groups, I think it shouldn’t be hidden like it is now, again needing an extra click to edit. Instead, allow to quickly adjust the filters in the quick filters, even when they are in groups:
I’m not sure everything should be editable by the editor. Adding new, personal quick filters, yes, but editing the groups, editing the “is” or “contains”, etc. I don’t personally think is needed. Then it allows for a cleaner UI and faster experience. All we need is a quick selector dropdown to pick values quickly to filter by.
All in all, I think it’s a step forward, but there is still improvements to be made to make the quick filters even quicker.
One more thought that came to mind after reading the Roadmap Item.
How do you plan to handle views showing multiple databases when adding a quick filter?
Is it the same UI as the current filters? Grouped by database?
This has been quite hard for some users to understand.
Idea: search for the fields, then within the search, group by “All Databases” and per database. This means users will search and find what they need, without needing think about what database to look for it in.
UI would need to clearly show that it is filtering for all databases, for example:
If I have a view with grouping, but default it will make the “Name=” for all databases (incl. groups) for end users, this might be confusing. The UI should make this clear.
Not needed for initial release, as they have been handling things just fine with the way things currently are in “Personal Filters”, but now that its more prevalent, more users will use, and more might get confused.
Of course, doing this without sacrificing functionality is not easy, but it would also solve this:
