change in dash behaviour in searches

[GianlucaFerri]

We recently upgraded to Nov2021 from Apr2020 and found a change in behavior in searches.

We have a field that contains values like

ABC-123

in which two values are separated by a "dash" character.

in Apr2020 dash was interpreted as a space in searches: writing the beginning of second part (i.e. 12) of ABC-123 would find it.

Now, in order to get the same behavior one must precede the search string with a *

this is painful for our customers, because the right part of the field is what they usually search.

Is there a way to set Sense to use the old matching method?

Thank you!