[BUG] Filter set to "is" acts as if it's set to "contains"

I’m having a lookup table in my view and I like to filter using elements from that table. I create a precise filter using the “is” statement. However, it does not work and other eletents also display – as if I had chosen “contains.” I’m now forced to exclude with an AND statement other elements, thus making my filter bloated. Please see here the screenshot: https://i.imgur.com/QhOjN4I.png

Welcome to the community, @Martin_M! :smiley: One thing to remember about lookup fields is that they contain (and return) arrays. The “is” filter condition is supposed to look for an exact match, but it appears that with an array, it’s currently satisfied to find a match with any one of the array items. I can see the case you’re making, and agree that the comparison should be more precise. I strongly suggest contacting Airtable support, sharing the same info you shared here.

In the meantime, there’s still a way to get what you want with some small tweaks. If you change your field from a lookup to a rollup, you can have greater control over the output, and create something that will work as an exact match for a filter.

The only meaningful difference between a lookup and a rollup is that a rollup lets you specify what to do with the array that it builds. This is done via the aggregation formula field. In your case, the formula could be:

ARRAYJOIN(values, ", ")

This will give you a string that looks the same as the displayed version of a lookup field, but will properly compare using an “is” filter condition.

1 Like