Document Chaining
What do you do when your model is so big to the point that isn’t usable and you can’t increase resources to your environment? I found that the best solution that worked for me is to split the model into smaller models while you keep one look and feel on the front-end. With this route I wanted my users to have an experience that makes them feel like they are in one app while they are jumping between apps. This brought the need of passing selections between apps. Like any other thing in Qlik it is doable. This is done through your URL on access point.
How it is done:
You will need the exact URL that goes to the model, once you have this you will have to add a simple code at the end of the URL to tell it what selections to pass or which sheet it should go to.
Passing Selections
- E.G. link &select=field, value &select=field2, “Value 2”
Link: This is the link that goes straight to your QlikView app.
field : This is the field ID you want to select when you get to the app. (E.G LB01)
Value is what you want to select when you get there. E.g. if you want to select a year you just put 2011.
If your value has more than word e.g. South Korea. You will need to use “” else it will do a fuzzy search. Looking for anything that has south and anything with Korea, meaning you might end up selecting North Korea, South Korea, South Africa.
Everything else you leave as is.
This example will be as follows:
Link&select=LB01,2011&select=LB02,”South Korea”
Landing Sheet
- E.G. link &Sheet=value
Link: This is the link that goes straight to your QlikView app.
Value: This is the Sheet ID of the Sheet you want to land on. E.g. (SH01)
The above example will look as follows
link&Sheet=SH01
Below is a link to a video by Qliktips
https://www.youtube.com/watch?reload=9&v=ESSvm_xMTlE
