Skip to main content
Announcements
Customer Spotlight: Discover what’s possible with embedded analytics Oct. 16 at 10:00 AM ET: REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
vlad_komarov
Partner - Specialist III
Partner - Specialist III

Handling [dash] and [single quote] by search objects

Hi all,

I've noticed that QV is handling two separate characters [dash --> [-] = chr(45)] and [single quote --> ['] = chr(39)] as identical string character in all search objects.

Example:

I've list of names where these characters are present:

1.png1a.png

Typing both of these chars in the search object returns the same result: QV selects both of them!

2.png 2a.png

They are clearly the different characters based on the ASCII code:

3.png

But for some reason, QV treats them the same way...

Not sure that I have a reasonable explanation for that. Any comments?

The sample app is attached.

I would appreciate any comments and/or suggestions...

Regards,

Vladimir

11 Replies
vlad_komarov
Partner - Specialist III
Partner - Specialist III
Author

Yes, looks like the same problem.

vlad_komarov
Partner - Specialist III
Partner - Specialist III
Author

It took a while, but I've got a response from Qlik Support:

____________________________________________________________________

According to bug# QLIK-14849 and QLIK- 15675 both describe this behavior is working as design  ( not a great design in my opinion), he is what R&D has explain about it:

"When you do global search for E and get a match on a word with É, the search suggestion will change the input line to É. The list of matches may contain words with either E or É.

Just as E and É sorts at the same position in all locales, hyphen and single quote sorts at the same position. Other punctuation sign (e.g. double quote, dot, plus) have higher and different sorting values, and these will not match each other, but hyphen and single quote happens to share search values."

I understand, hyphen and single quotes, are different character and the product should take it as different characters. For that I am going to reach the product manager team to look at this one more time, maybe (no guarantees) that we can make this better or at least documented so for future references and avoid any confusion.

____________________________________________________________________



Regards,

Vladimir