topic Re: Issue with Search in Field in QlikView

Issue with Search in Field

john_duffy — Mon, 12 Feb 2018 15:04:26 GMT

Hello All.

We have added functionality to allow our users to copy a list of values for an external source (eg. xls), paste the list into an input box and then search on the values. This saves the users having to key in the individual values. This works fine unless there is a QlikView key word in the search list (eg. NOT).

I have attached a very simple example of this scenario. In the example, the list received from the user contains 3 values - ABC, NOT and REF. Using the Select in Field action, we want the 3 values to be selected. Instead, all values except REF are being selected. QlikView is selecting ABC and every value that is not REF.

Any suggestion on how to handle this scenario? Keep in mind this is a very simple example. In reality, the list can contain hundreds of values and could potentially contain multiple values equivalent to QlikView key words.

Thanks.

Re: Issue with Search in Field

Anil_Babu_Samineni — Mon, 12 Feb 2018 15:16:18 GMT

Are you talking about "Current Selections" Wrong data?

Re: Issue with Search in Field

john_duffy — Mon, 12 Feb 2018 15:22:43 GMT

Hi Anil.

This issue is that the Select in Field action will not select the values in the Search String.

To see this scenario, click on the 'Select in Field1' text object. This will execute a Select in Field action for Field1 with search string (ABC|NOT|REF). The fields selected in the Field1 list box are not correct.

Re: Issue with Search in Field

marcus_sommer — Mon, 12 Feb 2018 15:24:26 GMT

I'm not sure if there is a really simple way of bypassing this behaviour but with some efforts to adjust the search-string it might be possible. In your simplified example would the following work:

("ABC"|"NOT*"|"REF")

- Marcus

Re: Issue with Search in Field

Anil_Babu_Samineni — Mon, 12 Feb 2018 15:28:56 GMT

Very strange, Not sure why this behavior running here. May be hic‌ helps

Re: Issue with Search in Field

john_duffy — Mon, 12 Feb 2018 15:31:34 GMT

Thanks for the suggestion Marcus.

This would work in this simple example, however, not in the production environment. The asterisk will select all values starting with 'NOT'. If for example 'NOTE' was another value, I would not want this selected. However, with "NOT*" in the search string, NOTE would also be selected.

Re: Issue with Search in Field

marcus_sommer — Mon, 12 Feb 2018 15:54:24 GMT

A different approach would be to embed your values within a search-expression, maybe something like this:

='=match(Field1, ''ABC'', ''NOT'', ''REF'')'

- Marcus

Re: Issue with Search in Field

john_duffy — Mon, 12 Feb 2018 16:45:24 GMT

Great suggestion Marcus. Thanks.

Re: Issue with Search in Field

hic — Tue, 13 Feb 2018 13:38:33 GMT

Unfortunately a bug. The best work-around is probably the one Marcus Sommer suggests.

HIC

Re: Issue with Search in Field

john_duffy — Tue, 13 Feb 2018 14:04:32 GMT

Thanks for the confirmation Henric.

Re: Issue with Search in Field

isingh30 — Tue, 13 Feb 2018 14:12:00 GMT

Hello Marcus,

What is this - ='=. If you can explain a bit.

Thanks.

Re: Issue with Search in Field

marcus_sommer — Tue, 13 Feb 2018 14:20:01 GMT

It's necessary to evaluate the content as expression. With just =match(Field1, ''ABC'', ''NOT'', ''REF'') it would be regarded as a string.

- Marcus

Re: Issue with Search in Field

hic — Tue, 13 Feb 2018 16:40:15 GMT

...or to be a little more specific: If you write

then the expression will be evaluated when the action is executed, and the result will be used as search string. This is not what you want.

But if you instead quote the expression

(and use two single quotes as an escape sequence for single quote) then the expression inside the quotes will be used as search string. I.e. the expression will be evaluated in the search context instead of in the action context. Which is what you want.

HIC

Re: Issue with Search in Field

isingh30 — Wed, 14 Feb 2018 13:58:57 GMT

Thank you Henric