Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Does anyone know if there is a way to preserve the current selections so that they are not cleared when the user selects from another field that excludes them?
Eg: I'd like the user to be able to select a team from a list box and then select a date for which there is no data for this team and have the team selection retained, so that they can continue to explore dates without losing their team selection. QlikView's default behaviour seems to be to clear the team selection in this scenario. Can this be changed?
The only partial solutions I've been able to come up with are to use the back button or bookmarks but I'd rather a solution that's transparent to the user.
Thanks in advance
Robin
Hi Robin,
You can lock your selections by
Selecting Lock in the Selections menu.
In your Navigation toolbar you'll see the Lock and Unlock icons
or you can use Ctrl+Shift+L to lock, Ctrl+Shift+U to unlock
If you lock your current selection any attempt to make a further selection outside the current one will not be accepted by QlikView.
Cheers
Andrew
Thanks Andrew, I tried that but it locks ALL selections. I need something that will allow selections but not clear those that exist when I select a value from another field that excludes them. Eg if I have a number of selections in pace and then click on a date which has no data for these selections it clears them all and I have to start again.
Regards
Robin
Hi Robin,
If I understand you correctly you want to make a selection outside the currently selected data. Unfortunately you can't do that and keep your current selections. If you try to make such a selection you're selecting data that is not associated with the existing selections.
If you have manufacturers Boeing and Lockheed selected then you pick Product Type: Shoes, no data could be returned. Rather than go blank QlikView will select Shoes and deselect the manufacturers.
Kind regards
Andrew
Yes Andrew, that is exactly it. It kind of makes sense for it to behave that way but users find it frustrating because they naturally want to explore the data without losing the context of the current selections when they try something that turns out to be not associated. I guess the best advise to give them is to use the back button or bookmark their selections?