Skip to main content
Solved

How does the interface list search work?


Kim_Trager1
Forum|alt.badge.img+20

I have an interface with a list layout. I was under the impression that when you searched the list it would search every visible column?

 

However when I search for fx “1073” it says there is nothing despite it being in my list?

Is this a bug, or is it me who is getting it the wrong way?

 

Search says there is no records
Records are there

 

Best answer by stagandforge

Not sure if you ever resolved this, but in case you haven’t (or someone else ever has a similar issue), there are some specific formatting quirks that may be causing this issue:

  • For the “straight up number input” field: make sure it’s set to not show the thousands separator, as this might be obscuring it from your search result if the # is rendered as “1,073” in your table. (Worth changing number of decimal places to “0” too, if you don’t need them here.)
  • For the concatenate field—if there are values immediately before “1073” in the field, that may also be why it's not showing up in the search. Sometimes search can be picky like that. ¯\_(ツ)_/¯ If you add a space right before the number value in the formula that may be enough to resolve it.

If those tweaks don’t work… well, I’m stumped.

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

8 replies

Saravanan_009
Forum|alt.badge.img+15

@Kim_Trager1

The list search in an interface with a list layout does not necessarily search every visible column. Instead, it typically searches only specific indexed fields. If "1073" is in your list but does not appear in the search results, it could be because the search function only includes certain columns, not all visible ones. Additionally, some searches may exclude numeric fields or require an exact match. Filters applied to the list could also impact search results. If the data was recently added, there might be a delay in indexing. If none of these factors explain the issue, it could be a bug, and checking system documentation or reporting the issue might be necessary.


Kim_Trager1
Forum|alt.badge.img+20
  • Author
  • Inspiring
  • 157 replies
  • March 17, 2025

Hi ​@Saravanan_009 

It’s pretty old data, so I don’t assume Airtable take months to index data..?

The two columns I’ve exposed is both a concatenation which I assume will be a string and the other is number field.

If I fx only search for 10 it will find other columns where 10 appear yet still exclude the 1073.

How can you make exact matches for a search in airtable?

  


Saravanan_009
Forum|alt.badge.img+15

Airtable’s search functionality does not always work with exact matches, especially in concatenated fields or number fields only. Can you please try the below method of steps?
1. Use Filters Instead of Search
2. Check Field Formatting
3. Use the Exact Match Operator in Search Extension
4. Create a Formula Field for Search Optimization
5. Test in Different Views


Kim_Trager1
Forum|alt.badge.img+20
  • Author
  • Inspiring
  • 157 replies
  • March 17, 2025

1. Use Filters Instead of Search

When I use filters that works - however the idea with the search is it’s a quick way to find something in your list.


2. Check Field Formatting

One of the fields is calculated column concatenating text and the other straight up number input.  


3. Use the Exact Match Operator in Search Extension

Do you mean using “1073” if so that does not give me anything.


4. Create a Formula Field for Search Optimization

I’ve created various formular fields concatenating a info together, however none of them pick up on 1073


5. Test in Different Views

If I add a grid view to it’s still the same. I’ve tried to take the tabs of but no luck either.

😬


stagandforge
Forum|alt.badge.img+3
  • Participating Frequently
  • 11 replies
  • Answer
  • April 2, 2025

Not sure if you ever resolved this, but in case you haven’t (or someone else ever has a similar issue), there are some specific formatting quirks that may be causing this issue:

  • For the “straight up number input” field: make sure it’s set to not show the thousands separator, as this might be obscuring it from your search result if the # is rendered as “1,073” in your table. (Worth changing number of decimal places to “0” too, if you don’t need them here.)
  • For the concatenate field—if there are values immediately before “1073” in the field, that may also be why it's not showing up in the search. Sometimes search can be picky like that. ¯\_(ツ)_/¯ If you add a space right before the number value in the formula that may be enough to resolve it.

If those tweaks don’t work… well, I’m stumped.


Kim_Trager1
Forum|alt.badge.img+20
  • Author
  • Inspiring
  • 157 replies
  • April 3, 2025

@stagandforge thanks for this, I still haven’t found anything to solve this. Mainly the straight-up number input that really throws me… However, you gave me an idea. It seems if I convert the number into a string, the search can pick it up 🙄. This can work for me as the number is a part id, so I don’t need to calculate anything with it except from being able to find it - which seems I’ll be able to now.


stagandforge
Forum|alt.badge.img+3
  • Participating Frequently
  • 11 replies
  • April 5, 2025

sometimes it’s just weird! might be worth shooting support a quick note about it, in hopes they might be able to make search operate the way we’d expect it to without weird workarounds, but obviously up to you. 

cheers!


Kim_Trager1
Forum|alt.badge.img+20
  • Author
  • Inspiring
  • 157 replies
  • April 7, 2025

I think I’ll do that...


Reply