In my table I have a column which uses a mapped option list. In that list the values are different from the labels. The values are numerical database foreign-keys, while the labels are those entities as strings. We can pretend that my table is a sales table and the option list values are product id's and the option list labels (which user sees) are the product names.
My problem is that filters won't work well on that column. Because if user sets a filter for "Bike" they get no match because the value is not "Bike", it's the corresponding id, say 123. So in these cases it would make more sense for filters to filter the labels rather than the values in option lists.
I went for a different solution where you don't need an addition column, and it can also be tailored for server-side pagination etc. However it will be a bit harder to implement for many operators since you have to apply the operator in you own code.
It's a pretty ugly workaround, but it works well. Full solution is described here:
