https://community.qlik.com/t5/App-Development/change-in-dash-behaviour-in-searches/m-p/1889661#M73287 <P>We recently upgraded to Nov2021 from Apr2020 and found a change in behavior in searches.</P> <P>We have a field that contains values like</P> <P>ABC-123</P> <P>in which two values are separated by a "dash" character.</P> <P>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.</P> <P>Now, in order to get the same behavior one must precede the search string with a *</P> <P>this is painful for our customers, because the right part of the field is what they usually search.</P> <P>Is there a way to set Sense to use the old matching method?</P> <P>Thank you!</P> Mon, 07 Feb 2022 09:35:07 GMT GianlucaFerri 2022-02-07T09:35:07Z https://community.qlik.com/t5/App-Development/change-in-dash-behaviour-in-searches/m-p/1889661#M73287 <P>We recently upgraded to Nov2021 from Apr2020 and found a change in behavior in searches.</P> <P>We have a field that contains values like</P> <P>ABC-123</P> <P>in which two values are separated by a "dash" character.</P> <P>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.</P> <P>Now, in order to get the same behavior one must precede the search string with a *</P> <P>this is painful for our customers, because the right part of the field is what they usually search.</P> <P>Is there a way to set Sense to use the old matching method?</P> <P>Thank you!</P> Mon, 07 Feb 2022 09:35:07 GMT https://community.qlik.com/t5/App-Development/change-in-dash-behaviour-in-searches/m-p/1889661#M73287 GianlucaFerri 2022-02-07T09:35:07Z