That's indeed an odd behaviour. I don't think it has something to do with your numbers, it doesn't even find textual values start with '-'.
You can find your negative values when you switch to fuzzy search:
and I think even using a single quote will find the negative values
IMO QV search is somewhat broken with regard to the minus sign, I checked hic 's blogs on the search subjects but haven't found anything relevant. Maybe the minus sign is a key word for the search itself.
Hopefully Henric can explain the issue.
I've noticed the same behavior too (Handling [dash] and [single quote] by search objects).
I've posted the question on QV Bugs forum (Handling [dash] and [single quote] by search objects) and have asked another question on Henric's blog (The Search String).
No clear solution/explanation so far except not very practical workaround suggestion to use '=index(Name,chr(39))' call as a search string....
Looks like a bug to me..
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.