Help

This Product Ideas board is currently undergoing updates, but please continue to submit your ideas.

Allow less exact searching for linked records

cancel
Showing results for 
Search instead for 
Did you mean: 
Mouser-IB-Admin
6 - Interface Innovator
6 - Interface Innovator
Status: New Ideas
What is the proposed idea/solution?

Right now when you search for a linked record, only exact results are returned. This means if I have a record titled "Texas State Fair - 2024 - Food", I cannot quickly grab that record by searching "Texas 2024" or "2024 food" because it's not exactly titled that way. I would have to type it all out, including hyphens, and if I had a lot of "Texas State Fair - 2024 - ###" records I'm going to have to look through them all every single time.

How does is solve the user problems?

Allowing a more relaxed search, semi-fuzzy of sorts, allows faster searching using the details a user remembers. It's very common to have the primary field of a table be a CONCAT formula to gather multiple pieces of data from a record (especially since you can only search for a linked record using that primary field and nothing else). By allowing less precise searches you can make it easier to find results, and there's nothing stopping a user from still being as exact as possible to further narrow down the results if they want. By loosing the tight restrictions, both types of search can still take place, but in the current design you can only use exact.

How was this validated?

Heavy use of linked records across multiple bases, and no ability to quickly search through thousands of records effectively to find the one I want unless I know its exact name in the primary field.

Who is the target audience?

Any Airtable user who has a base with linked records, especially if the base is large.

1 Comment
jord8on
7 - App Architect
7 - App Architect

We really need this! We have a linked table with thousands of product variants and a unique naming convention so we need the the form to allow users to type in keywords in ANY ORDER. Is there a workaround for this that anyone has found?