Help

Re: Filter options-- sometimes requires clicking 'APPLY' ... sometimes doesnt. 🤷‍♂️

190 0
cancel
Showing results for 
Search instead for 
Did you mean: 
GrahamW
6 - Interface Innovator
6 - Interface Innovator

Curious if this has happened to anyone else? ... and why? 

 

In one table, filter options now require that I click apply for them to take effect. See pic below. This is new. This table/view is one of our most regularly viewed tables and never required that. Changes to the sheet would happen live vs requiring clicking a button. 

GrahamW_0-1716557235059.png

The weird thing is too, on other tables, it's not required. We can still edit the filter options and the changes happen live. 

GrahamW_1-1716557375576.png


Curious what might have changed and if I can change it back? 

 

2 Replies 2
dsolimini
5 - Automation Enthusiast
5 - Automation Enthusiast

Graham --

I noticed this and I think it's a very clever fix to a problem that has given me all sorts of headaches over the years. I did a bit of poking around to "lightly" confirm my hypothesis... They've added the Apply button for views that have particular dependencies where instant filtering could cause unexpected/undesired results.

Ex: The Apply button appears when the view you are filtering is associated with an automation trigger. (There may be other situations where it appears, but this one I confirmed.) I created a dummy automation on a view and got the apply button in the filter -- note the warning at the top: 

dsolimini_0-1716558169916.png

So if you have an automation that sends an email to someone every time a record enters a view, live updated filters can cause a zillion emails to be sent without you intending as you make edits to filter conditions. (Will admit I've made this mistake...) This prevents that problem. I bet there are other situations where the filter button appears as well, but I haven't dug too deep. 

 

GrahamW
6 - Interface Innovator
6 - Interface Innovator

Oh interesting! Hmm.... I will have a look on it. 

Might be that an automation we made in a particular field is affected. I will look into this. Thank you !