When you use Set analysis, you can choose to have a condition in the form of a list of values in the Set expression, or you can choose to have a rule-based definition - a search for field values.
Examples of hard coded lists:
Sum( {$<Year = {2013,2014,2015}>} Sales)
Sum( {$<Country = {'Australia','Canada','France'}>} Sales)
Examples of searches:
Sum( {$<Year = {">=2013"}>} Sales)
Sum( {$<Country = {"Austr*"}>} Sales)
Sum( {$<Customer = {"=Sum(Sales)>100000"}>} Sales)
All the above constructions work today, and they will work correctly also after the bug fix.
Note the double quotes in the search expressions. These define the search strings, and between them you can write any search string – the same way as you would in a list box search.
However, you should not use single quotes to define a search string.
Single quotes are reserved for literals, i.e. exact matches. Hence they should be used when you want to make a list of valid field values, like the above list of explicit countries. But they should not be used for searches. Single quotes imply a case sensitive match with a single field value.
This difference between single and double quotes has been correctly described in the reference manual that states that searches are “always defined by the use of double quotes”. Also, all examples with literal field values in the documentation use single quotes.
Now to the bug: QlikView and Qlik Sense currently do not respect the above difference between single and double quotes. Instead, strings enclosed in single quotes are interpreted as search strings. As a consequence, it is not possible to make case sensitive matches with field values, something which you sometimes want to do.
This bug will be fixed in the coming November releases of Qlik Sense and QlikView. Then, wildcards in strings enclosed by single quotes will no longer be considered as wildcards. Instead, the strings will be interpreted as literals, i.e. the engine will try to match the string with a field value containing the ‘*’ character. The same logic will apply also to relational operators and equals signs.
Unfortunately, this bug has been incorrectly utilized by some developers: I have seen Set Analysis expressions with correct search strings, but erroneously enclosed in single quotes; for example
Sum( {$<Country = {'Austr*'}>} Sales)
This search should instead have been written
Sum( {$<Country = {"Austr*"}>} Sales)
Hence, there are documents with expressions that will not work in the corrected algorithm. However, the bug fix will be implemented in such a way that old documents will use the old logic, and new documents will use the new logic. In addition, it will be possible to force the new logic for all documents by using a parameter in Settings.ini.
You can of course also change the single quotes in existing search strings to double quotes, and the expression will continue to do what it always has done.
This post is mainly to give you a heads-up on a coming change, and give you a chance to make a quality control of your own documents. We will publish more information as we get closer to the release.
HIC
Further information related to Set Analysis and Searches:
The Search String
Introduction to Set Analysis (video) - Part 1
Set Analysis - Part 2 - Cool Stuff You Can Do (video)
.png "Former Employee"){kind=icon}