Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Solutions in QlikView :
"mark this variable for inclusion in bookmarks and it will survive reloads. (Settings > Document properties > Variables > Settings for Selected Variable > Include in Bookmarks)".
How to do this with Qlik Sense ?
These variables are used in the report to manage the displays.
The values are therefore specific to each user during their session.
The reload done by the QMC, resets these variables, and therefore the user loses his display.
It's normal when I enter a session but it's abnormal during my session
There should be a specification at the level of a variable that says whether the value of the variable is saved after a reload or not. This specification should be available in the "variable imput" extension or in the definition of variables.
Is there anyone in the community who has the same problem?
What solution did you use to get around this problem?
It seems that this is not supported by Qlik Sense. To put it in a future release, the issue needs to be requested by more users.
New remark (23/08/2022):
Actually, to solve the problem, I had to create island tables to put the possible values of the variables in dimensions. This way, instead of entering a variable value, I select a dimension that will be the value of my variable and these dimensions are saved on reload.
The goal of a new version of Qliksense would be to save the variables that have been defined as variables to keep on reload. In this case, table islands would no longer be necessary.
BUT, the creation of bookmark saves the dimensions but not the variables, SO when a bookmark is created, the selected dimensions as well as the variables to keep on reload should be saved in the bookmark .
Bookmark
When creating a bookmark, it would also be very interesting to be able to select the option "Make bookmark apply on top of current selection" (option we have in Qlikview)
Hello all,
I got confirmation that is is working as intended. I also tested some old versions as November 2020 and the behaviour it the same as May 2022.
As you said, it might be worth to raise an Idea or explore other alternatives as you are already doing.
Cheers,
Albert