Skip to main content

Search results on Interface aren't accurate

  • July 30, 2024
  • 6 replies
  • 74 views
R
Forum|alt.badge.img+4

Hello,

Our team has recently started taking advantage of Interfces though we've noticed the search feature seems to work differently than in a regular Airtable data table. In the first picture I provided you can see that searching "BCTS220" returns two results with "BCTS220-1R" existing in each (this is accurate). But if you search for  "BCTS220-1" it only shows one result even though that string exists in the the other record which isn't being shown. 

Does anyone know how searching in Interfaces is different or if there's a way to correct this?

6 replies

TheTimeSavingCo
Forum|alt.badge.img+31

Hm I tried to recreate your issue here but it seemed to work fine:

I take it that we're searching by the "PHS PN Log AS-2133" field?  Could you provide a screenshot of that field of the record that isn't showing up so that I could try to recreate the data exactly? 

Could I also check what field type it is?

Adam, Airtable Consultant - thetimesaving.company
R
Forum|alt.badge.img+4
  • Ruffruff66
  • Author
  • New Participant
  • July 31, 2024

Hm I tried to recreate your issue here but it seemed to work fine:

I take it that we're searching by the "PHS PN Log AS-2133" field?  Could you provide a screenshot of that field of the record that isn't showing up so that I could try to recreate the data exactly? 

Could I also check what field type it is?


Hi Adam,

Yes in this instance we're searching by that field, but there's no filter in place to ensure it's only searching there. If that string showed up in any other column it should also show up as a result.

The record that isn't showing up only has "BCTS220-1R" while the record that stays includes this as well as many other part numbers.

The field is a link field that pulls number from a separate log which houses our part numbers.

Not sure if that helps answer your questions.

TheTimeSavingCo
Forum|alt.badge.img+31

Hi Adam,

Yes in this instance we're searching by that field, but there's no filter in place to ensure it's only searching there. If that string showed up in any other column it should also show up as a result.

The record that isn't showing up only has "BCTS220-1R" while the record that stays includes this as well as many other part numbers.

The field is a link field that pulls number from a separate log which houses our part numbers.

Not sure if that helps answer your questions.


re: Yes in this instance we're searching by that field, but there's no filter in place to ensure it's only searching there. If that string showed up in any other column it should also show up as a result.

Yeap, you'd need to use a filter for that instead of the search function

---
Hmm, yeah, based on what you've described I think I set up my base in a similar way and it displays both records as expected.  If you could provide a read-only invite link to a duplicated copy of your base with some example data I could take a look at this for you! https://support.airtable.com/docs/adding-a-base-collaborator#adding-a-base-collaborator-in-airtable

Adam, Airtable Consultant - thetimesaving.company
R
Forum|alt.badge.img+4
  • Ruffruff66
  • Author
  • New Participant
  • August 2, 2024

re: Yes in this instance we're searching by that field, but there's no filter in place to ensure it's only searching there. If that string showed up in any other column it should also show up as a result.

Yeap, you'd need to use a filter for that instead of the search function

---
Hmm, yeah, based on what you've described I think I set up my base in a similar way and it displays both records as expected.  If you could provide a read-only invite link to a duplicated copy of your base with some example data I could take a look at this for you! https://support.airtable.com/docs/adding-a-base-collaborator#adding-a-base-collaborator-in-airtable


I was making a sample interface for you to test the issue yourself and came across something interesting. It looks like this issue with the search feature providing inaccurate results only occurs when doing so from the user view. In the public read-only interface this issue is non-existent. Any idea why this might be? 

TheTimeSavingCo
Forum|alt.badge.img+31

I was making a sample interface for you to test the issue yourself and came across something interesting. It looks like this issue with the search feature providing inaccurate results only occurs when doing so from the user view. In the public read-only interface this issue is non-existent. Any idea why this might be? 


Weird!  I've just tried testing that and it worked fine for me

Here's a public view:

Here's a read-only interface:

And here's an editor interface:

Adam, Airtable Consultant - thetimesaving.company
R
R
Forum|alt.badge.img+4
  • Ruffruff66
  • Author
  • New Participant
  • August 8, 2024

Weird!  I've just tried testing that and it worked fine for me

Here's a public view:

Here's a read-only interface:

And here's an editor interface:


Hmm, definitely weird indeed. The issue seems contained on our end even if we don't understand it yet. 

Thank you for your help though Adam!

TheTimeSavingCo
Terms & ConditionsAccessibility statement