Skip to main content
Solved

Filtering no longer dynamically updates

M

Up until yesterday, when I changed a filtering option, the table would automatically update. Now it doesn't and I have to hit apply to see the changes.

I use filtering a lot to test my data - I look at a summation field and check, for example, what is the result when field X >1? >2? Etc. With the filtering dynamically updating whenever I changed it, I'd get instant feedback. Now it's a real chore, not only do I have to hit apply, but the filter box goes away and I have to reopen it, go to my filter choice, and enter my next value to test. 

Am I missing something? Is this an intentional update? Thanks!

Best answer by TheTimeSavingCo

I think it pops up on tables where there's a lot of records / views?  I've got a table with 110 fields and the "Apply" button for the filter starts showing up once I hit 4465 records exactly

On another table with 4465 records and 3 fields the "Apply" button doesn't come up, and that's why I think it's a combo of the records / views heh

View original
Did this topic help you find an answer to your question?

7 replies

Saravanan_009
Forum|alt.badge.img+5

It sounds like you’re experiencing a change in behavior with Airtable’s filtering functionality. This could be due to a recent update or change in Airtable’s interface. Here’s what you can check:

Filter Mode: Make sure you haven’t accidentally switched to a different filtering mode. Sometimes, interface changes might alter how filters are applied or displayed.

Browser Cache: Try clearing your browser cache or using a different browser to see if the behavior persists. Occasionally, cached data can affect how web applications function.

Airtable Updates: Check Airtable’s release notes or blog for any recent updates or changes to their filtering functionality. It’s possible that there was a change in how filtering works or a new feature was introduced that alters the default behavior.

ScottWorld
Forum|alt.badge.img+20
  • ScottWorld
  • Brainy
  • 8748 replies
  • August 28, 2024

@Michael_Morris2 

Airtable has never explicitly spelled this out in their support documents, but the Airtable consultants have figured out that the “apply” button shows up if there are other dependencies that are based on that filter which could get messed up by changing the filter.

For example, syncing to external bases is one of the situations when the “apply” button will appear.

Hope this helps!

— ScottWorld, Expert Airtable Consultant

M
Saravanan_009 wrote:

It sounds like you’re experiencing a change in behavior with Airtable’s filtering functionality. This could be due to a recent update or change in Airtable’s interface. Here’s what you can check:

Filter Mode: Make sure you haven’t accidentally switched to a different filtering mode. Sometimes, interface changes might alter how filters are applied or displayed.

Browser Cache: Try clearing your browser cache or using a different browser to see if the behavior persists. Occasionally, cached data can affect how web applications function.

Airtable Updates: Check Airtable’s release notes or blog for any recent updates or changes to their filtering functionality. It’s possible that there was a change in how filtering works or a new feature was introduced that alters the default behavior.


Thanks for your tips. I don't understand how to switch between filtering modes. I looked it up and found things on dynamic filtering, but it looks like it maybe only applies to linked records? This is not my case. I tried a different browser with the same results. Lastly, I don't have the patience to sift through release notes. 😉

 

M
ScottWorld wrote:

@Michael_Morris2 

Airtable has never explicitly spelled this out in their support documents, but the Airtable consultants have figured out that the “apply” button shows up if there are other dependencies that are based on that filter which could get messed up by changing the filter.

For example, syncing to external bases is one of the situations when the “apply” button will appear.

Hope this helps!

— ScottWorld, Expert Airtable Consultant


Thanks Scott. I don't think I have any dependencies on this filter. This seems to be an issue for me on all my tables in this database. If it was a dependency issue, wouldn't it only apply to particular tables? Interestingly, I did check another database of mine and that does not have the Apply button, so clearly I did something to make the Airtable gods angry with this database, but I can't think what it might be. Is there a way to check dependencies of a filter?

ScottWorld
Forum|alt.badge.img+20
  • ScottWorld
  • Brainy
  • 8748 replies
  • August 28, 2024

Hmm… I’m not sure. It’s always possible that Airtable might be slowly rolling out the “Apply” button feature to all bases. You may want to email support@airtable.com and ask them why the Apply button sometimes appears and sometimes doesn’t appear. Be sure to report back with what they tell you!

TheTimeSavingCo
Forum|alt.badge.img+18

I think it pops up on tables where there's a lot of records / views?  I've got a table with 110 fields and the "Apply" button for the filter starts showing up once I hit 4465 records exactly

On another table with 4465 records and 3 fields the "Apply" button doesn't come up, and that's why I think it's a combo of the records / views heh

Adam, Consultant @ The Time Saving Co
M
1 person likes this
  • M
    Michael_Morris2
M
TheTimeSavingCo wrote:

I think it pops up on tables where there's a lot of records / views?  I've got a table with 110 fields and the "Apply" button for the filter starts showing up once I hit 4465 records exactly

On another table with 4465 records and 3 fields the "Apply" button doesn't come up, and that's why I think it's a combo of the records / views heh


This is it! I had been adding several new fields when this became an issue. You had 491,150 cells (fields * records) and I had 558,108. I deleted a bunch of old fields that I no longer use, getting me down to 486,459 cells, hit refresh, and Apply went away. Big thanks!  Now I'll have to weed out more records, maybe dump them to a different table, to keep that from happening again.

TheTimeSavingCo
1 person likes this
  • TheTimeSavingCo
    TheTimeSavingCo

Reply


Most helpful members this week

Terms & Conditions