Collation vs. Flexmonster

Hello Flexmonster-Team,

recently we noticed an "interesting behaviour" while using filters on our custom datasource.

Our specific case:
A customer wanted to filter some values for specific cities only. As it happens the city appears in our database with 2 different (viable) spellings: "Großenlüder" and "Grossenlüder". Flexmonster offers both variations in its filter options. But, unfortunately, our database cannot differentiate between those two.

We are using a non-binary collation, so if we select any city containing "ß" we would receive both results.

So when a user selects any of those options in the filter, the resulting query would return all rows with any of the two spellings. But, we suspect, Flexmonster does not expect more than the one spelling that was chosen. So it creates a row for each set that has the selected spelling but not for the other spelling. But as our database still returned those values the sum still consists of all data.

I hope the attached screenshots can help to understand the problem.

Since it's not possible for us to change collation, we were wondering if there is something on your end you could think of to resolve this issue (that, we suppose, might affect other german-speaking customers as well?)

Kind regards,
Florian