Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
After selecting some dimensions in a sheet, when we select an unavailable dimension, it will clear previous selections and generate unintended charts.
How to produce it?
Is there a way to make the unavailable dimensions which are in dark grey background to be not selectable or remove from the list?
Thanks and regards
I don't think it's a bug, that's how QlikSense associative engine works since I started with.
The dark grey color should give your users a clear indication that the value is excluded from current selections, so selecting the excluded will render the current selections invalid.
If you want to hide the excluded, there was an option for that in QlikView, I am not 100% sure about the latest options for a filter pane in QlikSense, but a calculated dimension like
=Aggr([Region Name], [Region Name])
in your filter pane should hide the excluded as well.
I don't think it's a bug, that's how QlikSense associative engine works since I started with.
The dark grey color should give your users a clear indication that the value is excluded from current selections, so selecting the excluded will render the current selections invalid.
If you want to hide the excluded, there was an option for that in QlikView, I am not 100% sure about the latest options for a filter pane in QlikSense, but a calculated dimension like
=Aggr([Region Name], [Region Name])
in your filter pane should hide the excluded as well.
One alternative is to lock the field after making selections.
-Rob
It is designed it that way, but it could misrepresent the selected data from a user perspective.
As an example: in the same sales discovery app, under "Past dues" sheet, select region as Central, and State as IA. then search Customer "A1 datacom Supply" in the Table header and select it.
Now some users could get the impression that "A1 datacom Supply" also operates in Central region of IA State.
For now, i will try to freeze the fields after selection as Rob had Suggested, but that will reduce the features of application, and is not a proper solution.
Any other suggestion?
Thank you for your inputs.
As Stefan mentioned, QlikSense (and QlikView I believe) have always worked on the basic principle of the three (or four) colours:
That said, with QlikSense, selections are kept at the top to give you an easy way to see what your views are visualizing.
Like you said, the previous selection will be removed and thus, there won't be any confusion to the user what they are looking at, as it is no longer there.
This is just something that your users will have to learn, or that you should teach them.
I agree with Tim, if your users do as you described above, filtering the customers for A1 datacom Supply will show the value in grey, indicating a value excluded from current selections.
If your users select this value, the current selections won't show the selections in region and state, so there should be no reason to assume that this customer is linked to this region / state.
It's vital that your users understand how Qlik's associative engine works (what the colors are indicating).
In a small scope of users, it makes sense to train them.
What i had described is just an example.
We are using the mashups and visualization API to generate those components and make the data accessible to general public, and in some instance, to specific groups of users, using web applications.
Some users will search and click those dark grey(not associated) options, which would generate charts with unintended information.
So it would be great if there were some option to enable/disable visibility of those not associated data from the table/filterpanel search, atleast in the mashup API.
For the moment, i am going to convert all the dimensions to =Aggr([Region Name], [Region Name]) format.
We hardly have to speak about training here.
One info sheet where the colours are explained, with or without example, is often enough to make it quite clear to new users.
On top of that, as mentioned, the selection bar at the top in Qlik Sense helps a lot with stopping people from making assumptions as it literally tells you how you're limiting your data.
If you are doing mashups, why not make your own listbox?
-Rob