Issue with Search in Field

[john_duffy]

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.

[Anil_Babu_Samineni]

Are you talking about "Current Selections" Wrong data?

[john_duffy]

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.

[marcus_sommer]

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

[Anil_Babu_Samineni]

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

[john_duffy]

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.

[marcus_sommer · Accepted solution]

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

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

- Marcus

[john_duffy]

Great suggestion Marcus.  Thanks.

[hic]

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

HIC

[john_duffy]

Thanks for the confirmation Henric.