Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
heyzain123
Contributor
Contributor

Compound Search

Hi - I am new to QlikSense and struggling with the compound search in Filter Pane. As in image 1.png, I want to select only records containing strictly "Acton" or "Action Park" but the expression seems to yield no results as in image 2.png.

Please help!

Zain.

5 Replies
marcus_sommer

If there are any spaces or special chars in the search-string it must be wrapped with double-quotes. Depending on the used place a search of (s|t) might not be recognized as search and needs as a whole to be wrapped with single-quotes. This means your search-string should be look like:

("Acton"|"Acton Park")
   or
= '("Acton"|"Acton Park")'

Many more background could you get here: Compound-Search-demystified.

Beside this I got the impression that both values - and also the ones in upper()  - are the same. If you should consider to harmonize them, maybe with a Mapping.

- Marcus

heyzain123
Contributor
Contributor
Author

Thank you Marcus - it worked!

heyzain123
Contributor
Contributor
Author

Hi Marcus, sorry to bother again. I have another question..

My filter expression for the filter pane is quite large (about 1000 chars) but the filter pane allows 255 characters to be typed in. Is there a way to increase the character limit ? Please see the attached screenshot for more clarity.

I use QlikSense desktop latest version.

Thanks,

Zain.

naveenjinkala
Contributor II
Contributor II

Initialize a variable with the search string and try using it.

marcus_sommer

I don't know if and when how the max. number of chars could be increased within Sense. AFAIK the limit in View are 1024 chars - this means that the search-selection logic itself could handle more chars but here in Sense it might be intentionally restricted to minimize the amount of data which is transferred between the object and the engine.

In View it was quite common to use variables for cases which hit these limitations and a following action/macro applied then the selections or the variable itself was used as filter within a set analysis - both approaches should be viable with the help of extensions (or maybe already natively today?).

Beside this you may save some chars by implementing some wildcards in the search-string, for example with:

...|"B*General*"|...|"A*General"|...

and it may also an alternatively to shorten the field-values within the script and/or to create some main/sub groupings for them and/or to create some flags for the most common search-strings.

- Marcus