I have common Dashboard for different products. I wanted to create some control page which was only displayed initially to the user when they did click the .qvw from Qlikview access point, there it will have some options to choose like Product, Language, ...etc. Based on user option from Control page, rest all views will be decided and visible.
Shoham, Thanks for your suggestion. I could have used one variable. Actually,this is not customer requirement, we've Dashboard which was created our in-house team in java and we've adopted recently Qlik and we should migrate all customer apps to Qlik asap. So, every thing must be same as is unless there must be ask. May be I'll convey this later point of time.
Peter's response above covers the basic idea, but just a quick tip - instead of checking fields or variables for being marked, if you want this landing page to only display once, create a vShowLandingPage variable in your QVW, set it to 1 by default, and add an OnLeaveSheet trigger for the control sheet that sets it to 0. Place this variable in the Conditional section of the Show Sheet option.
Thanks you! Peter, Varun & Shoham. It helps so much.
I wanted My Dashboard in below way...
When I opened .qvw, it should be display only Control Page, after user selection, user hits submit button it enables rest all tabs and vanish the Control or Home page. This should be remain as is every time user opened Dashboard. qvw.
So, what I did here is, I created two variables vShowLandingPage and vShowViews, I set vShowLadingPage=1, which opens landing page initially and vShowViews=0 which hides other views, after user selection on Home page and submit button at same Home page, values of these two variables get exchange i.e, vShowLandingPage=0 and vShowViews=1. So, now Home page gone and rest all tabs will appears...
As of now I'm okay with this, but, appreciates, is there any best way that makes client more happy other than this ?
I guess, I'm asking many questions, but, I don't have option since I'm very new to Qlikview.
It sounds like you've got it about right - though you could have just used a single variable if you wanted, rather than two, the result is the same.
I'm not sure why your client would be unhappy about you doing exactly what they asked, so I can't say if there's a way to make them happier. Conceptually, I don't like using landing pages in QV - I feel that it lowers usability. I prefer a starting sheet and a default set of selections (which can be set based on the user logging in) to a menu / landing page. However, customer requirements are customer requirements..
Shoham, Thanks for your suggestion. I could have used one variable. Actually,this is not customer requirement, we've Dashboard which was created our in-house team in java and we've adopted recently Qlik and we should migrate all customer apps to Qlik asap. So, every thing must be same as is unless there must be ask. May be I'll convey this later point of time.
