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 recordsRecords 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.
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.
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
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.
@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.
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.