Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
we have an app that is quite huge. In a standard selection list filter box we have e.g. a list of products. When a user selects a value in the list (but not yet confirms the selection), QlikSense is starting to filter the sheet after a moment automatically (which is standard behavior afaik). This results in a refresh of the list (selected to top, not selected values greyed out). As the app data is huge, there is a visible delay of 2 seconds before it is refreshed.
If a user wants to select multiple values, the system starts to execute the query and the user cannot select more values without having to wait and basically start over. Also, people get confused by the white values turning grey / resorting of the list.
Can we somehow prevent the immediate execution of the new filter set and instead only refresh once the green checkmark is really checked (or once the focus of the object is removed by clicking somewhere else)?
Thanks!
the on-the-fly evaluation of the data set is a built in functionality of Qlik engine. i do understand that if the data set is huge and your visuals take time to render this will be annoying. you can perhaps take two approaches. first you can use ODAG - this however carries a different user experience so you need to evaluate if this will work for you (too long to explain so you need to look it up). another way is to create your filter as an island table.
ill explain the second approach - if you get a distinct of the field you want to filter for and load it in a different field name in a table on its own, then selecting one or more from it does not influence the data set. afterwards there will be a couple of approaches how to use. you can create a variable that collects the selection and use that variable in your set analysis, or you can create a button (like APPLY SELECTION) and an action that selects the actual field using the values that were selected - this way the visuals are not rendered using individual selection values.
the on-the-fly evaluation of the data set is a built in functionality of Qlik engine. i do understand that if the data set is huge and your visuals take time to render this will be annoying. you can perhaps take two approaches. first you can use ODAG - this however carries a different user experience so you need to evaluate if this will work for you (too long to explain so you need to look it up). another way is to create your filter as an island table.
ill explain the second approach - if you get a distinct of the field you want to filter for and load it in a different field name in a table on its own, then selecting one or more from it does not influence the data set. afterwards there will be a couple of approaches how to use. you can create a variable that collects the selection and use that variable in your set analysis, or you can create a button (like APPLY SELECTION) and an action that selects the actual field using the values that were selected - this way the visuals are not rendered using individual selection values.
Thanks Edwin,
that helps - ODAG is not really applicable in this case and also the second option is not really feasible as we have ~20 different filter fields that have this issue.
Nevertheless, two good suggestions.
I was hoping for a parameter for the app that the query-auto-execution could be delayed or the "green checkmark" to be enforced...
Thanks again,
Bernd
- "query-auto-execution could be delayed " that may be something you can throw to Qlik. itll be interesting is it does exist.