Help with IN() Expression evaluation

I have an app that uses slices that allow users to filter and query data collected in another app. The expression that made these slices work was:

IN([column], Query[column])

It seems that this expression is still working fine for most of the columns that are being evaluated, but it looks like something may have changed with how this expression is being evaluated with columns with multiple values (the data is being collected in ENUMLIST columns).

So if the possible values in the ENUMLIST for [column] are “a, b, c”. When a person populated the Query[column] with “a”, they used to get back any rows that had values with “a” in them, ie “a”, “a, b”, “a, b, c”, “a, c”. Now however they are only getting rows with “a”. If they populate the Query[column] with “a, c”, they will get rows with “a” and rows with “c”, but not rows with “a, c”.

Is there a simple way to change this so that it functions the way that it used to? CONTAINS would let someone find “a” in an “a, c” row, but I’d have to limit what my users search by to one value at a time.


If you are searching a table of date for an “a” and “c” from an ENUMLIST, then you are actually trying to compare 2 lists. IN() wont work in this senario but this will:


Thanks Simon, that did the trick.