Has anyone else noticed a change in how the wherecontains function works? S

- Just tested in all versions from 6.6.0 to 7.7 and it has always worked this way, without duplicates in the result.
- I don't' have any other set function in mind that would help in this case on top of my head but can you describe the use case to see if there's another option other than looping?

I'll also let other throw out ideas on this one, but wanted to clarify that the behavior has been the same since the beginning of this function to avoid confusion

Very interesting - That goes against my experience as I've used it extensively in 6.5, 6.6 and 6.7 and it's never removed duplicate results from the result set before.

My use case is that I have a large list of Id's and I need to get a corresponding object for each ID. Because there are only ~30 objects and they live in the database I wanted to use the wherecontains and index function to transpose the ids into the objects via:

index(objectArray, wherecontains(keyList, objectArray.Id), null())

I've used this successfully in many situations and have even created an expression rule to use this recipe in shorthand.

use this: apply(wherecontains(_, {a, b, c}), {a, b, a})

copy paste this and hit Test Rule button in rules editor: =apply(wherecontains(_, {"a", "b", "c"}), {"a", "b", "a"})

Thanks Ganesh. I actually ended up using an apply with displayValue instead but that would definitely work as well.