This is the thing I was thinking about many many many times:
would you mind to add the enable/disable switch to filters, sort and group section? The same switch that is already implemented in search box, hidden fields and in filters.
In filters it is present only to disable them all, but not separate/selected filters or filter groups, or selected filters inside filter groups, which could be very useful.
The same in sort, where I could temporarily disable some sort criteria while others keep active.
And switches can be useful also in colors section to temporarily disable selected coloring criteria that I donāt want to delete and then create again later.
This could be very handy, time-saving and useful when manipulating with filters, sorting, rows coloring and grouping. The whole workflow could be much more flexible and versatile, without need of creating more and more views just because of one differen filter, sort, color etc.
Hello @marcus, weāve discussed your proposal. Weāre concerned that adding too many switches might overcomplicate the UI. Currently, we have a switch for filtering āall disabledā which, for some users, is already confusing. So, we are rejecting this feature idea, but we will implement the switch to delete the whole filter group. Hope for your understanding!
@olgatrykush Please reconsider adding a on/off toggle for each filter. I feel like Iām deleting and re-adding filters all day instead of simply turning them on/off.
I canāt see why this would be confusing UI, but perhaps this feature can be enabled for more āadvancedā users in the Settings?
Hey @marcus@avviodigital, weāve talked again about this idea and it has been approved. Our new plan is to replace the trash bin icon with the three dots āā¦ā, and place two actions underneath ā delete or deactivate filters. What do you think about this implementation?
Hey @marcus, Iāll leave your suggestion as a comment under the issue addressing this feature request. When someone from the development team picks it up, theyāll sync with our designer to decide on the best solution. Thanks for your input!
(The issue should be created by the end of the week. Iāll share it here once itās live.)
It seems to me that with version 1.31.1 there was a change in some filters behaviour.
As a workaround for the toggle/on-off functionality for individual filters my team used to just leave some filters blank, but now this seems to lead to a variety of issues for some larger tables and more complicated filter setups.
issues like:
leaving the filter blank now actually applies certain filters - I assume for fields which distinguish between empty vs null - and the result is that we either need to delete these filters and set up again a bunch of complicated filter setups Or come up with new ways of workign with views/filters
this change also seems to lead to rows skipping after mouse click and seemingly random order/sort changes for filter which have been set up prior to 1.31.1
anyways - this feature (toggle) would really save a lot of people a lot of time
leaving the filter blank now actually applies certain filters - I assume for fields which distinguish between empty vs null
Do you have any specific field type/filters combination in mind? For sure, empty values have no effect in some lookup/formula field type/filter type combinations, where values are stored in an array. Weāve introduced some new filters for lookup/formula field types in 1.31.
this change also seems to lead to rows skipping after mouse click and seemingly random order/sort changes for filter which have been set up prior to 1.31.1
with such config - clicking a random field (text in my case) causes the filter to āupdateā and show the message in the screenshot.
for context - not sure if related - we generated a lot of AI responses with select options (choice output type) and then we used formulas to extract the value for filtering.
Overall - filter/sort issues still seem to come up more often for single/multi select fields.
As for the second issue with āskippingā rows -
it is very similar to this - Sort broken for single select fields in large tables
After applying sort - clicking a row causes it to change order (but I havenāt had a chance yet to dig deeper, as I did in the linked case).
Anyways, I noticed this in conjunction with problems with updating tables after scroll or seeing a āliveā update of values via N8N flow. Again - not sure if this is directly related, but,
before the update to 1.31.1, I would see the new values updated by N8N row by row show up āliveā. Right now - the table stops showing the updates after a while (like a few dozen values get updated and then I have to refresh the page to see the new values).
This also coincides with AI fields failing to show the answers without a page refreshā¦ so kind of similar story.
Again - not sure if this is related, and I would probably need to investigate this further to provide a list of reproducible steps. Still, I was reaaaaaally hoping that such bugs were a thing of the past in Baserow.
