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

Announcements
Save $650 on Qlik Connect, Dec 1 - 7, our lowest price of the year. Register with code CYBERWEEK: Register
cancel
Showing results for 
Search instead for 
Did you mean: 
pravinboniface
Creator III
Creator III

Qlik Button chart requires me to click twice

I posted earlier about this problem.  I have a large table of ids.  The user wants to be able to filter for hundreds of Ids by copy-pasting from Excel into a text box and clicking a button to filter the dashboard for the ids the user needs.  Bookmarks will not work as the list of Ids will change frequently.

I have a table with ids.  I am providing an input box to enter a search argument in Qlik Compound search syntax, for eg (0001|0005).  The input box will load the value into a variable.  I have a Button chart that has an action to "Select values matching search criteria" which will take the values from the variable and filter for the ids.

The problem is that I need to click the button twice.  Why is that?

 

On Qlik cloud, it looks like you always have to click twice.  The first click sets the variable with the input box value.  The 2nd click seems to perform the match action.

On Qlik enterprise, if the column has a different value selected, it takes one click.  Else it needs two clicks.
pravinboniface_0-1761417116809.png
Thanks in advance for your help!

Labels (5)
2 Replies
Kaushik2020
Creator III
Creator III

could you pls suggest why the default way of searching is not applied. the search icon in your table can actually do this job. restrict the table to show only restricted records (straight table with pagination). alternatively a filter pane ?
Pls share more details on the certain way of implementing this way of search in sheet.

pravinboniface
Creator III
Creator III
Author

Thank you for your response.  I do agree there are better methods, but this has to do with a lot of users used to this method.  The older button extension did not have this issue, but it's the newer one now included in Qlik that seems to have this problem.  I'm sharing the app if you want to see the details of the implementation.