Selection in one sheet should not be reflected in other sheet

[#1]

Hi all,

i am using 8.0 version of qlikview .

in that i want to make selections in one sheet but should not be reflected in other sheet ,

but if i come back to the previous sheet selection should be as it is .

Please ,help me

[#2]

manzo.rob wrote:I am a relative novice to QV but am trying to create charts with preselected values. Some of our executive users want to be able to select a chart with values already in place. We are creating something of a menu for them to chose from. For example - Customer Sales for Region 1, Customer Sales for Region 2. They do not want to have to select the region from a select box.

John Witherspoon wrote:There are a couple ways that I've used. First, you can use set analysis.

Why set up (unsupported) macros to do essentially what a bookmark was designed to do? In your example macro you are enabling / disabling expressions within the chart which I admit, I don't think actions/bookmarks can accomplish... but it doesn't seem that level of sophistication is required here.

The easiest way to create a pre-built catalog of selections and chart states is to simply click the Add Bookmark button on the bookmark toolbar, name it what you like (for example - Customer Sales for Region 1), and make it a document bookmark.

Be sure to check the boxes for "Make this bookmark a document bookmark" and "Include Layout State" - this means the bookmark will be there when your end user opens the document later, and when they select that bookmark thy will be whisked to the Sheet, selections, object states, etc. that were set up when you created the bookmark.

Now you can point your executive to the list of bookmarks you created for him... and hopefully along the way he learns to make some bookmarks of his own

[johnw]

kevin.littich wrote:Why set up (unsupported) macros to do essentially what a bookmark was designed to do?

When I put that application together, bookmarks were what I tried first. They were woefully inadequate to the task. Perhaps they've improved greatly since then, as this is a very old application (four or five years?). Perhaps I was doing the community a disservice to be cutting and pasting code from such an old application instead of looking for better solutions. If I were writing this application from scratch, I would again try to do it with bookmarks first, but there's a lot in there that isn't really default bookmark behavior, so there would likely be a lot of issues to resolve. But if the need could be met with bookmarks, that would likely be a better approach.