Bob,
Document chaining could be used in several cases all of them revolving around more scalable use of resources:
- Security: let's say all users can see one "welcome" QlikView app, and then only a few should see details. Instead of creating a complicated section access and sheet level security implementation all in the same app, which will be very difficult to maintain, you move those analyses to a different QVW to which only selected users can access,, but the overview is visible to all.
- Performance:
- if you have several apps with the same logic, like sales per country, it would be useful to have one app for each country instead a huge app with all countries which lots of rows that most of the users do not use, because they always preselect their region and then analyse from there
- if you have historic data which is not always the main point of analysis, you can have Year 0 and -1 in App1, Year -2 in App2 and Year -3 in App3.
- Drill-down or guided navigation: there are lots of apps in your deployment, each of them with different levels of granularity or simply sharing a few common fields (some date or type of person or item ID). Instead of creating a very complex galaxy schema you can create smaller apps with their own star dimension-fact tables and allow the users to jump from one view to another
Which is common to all and the other most important feature of Document Chaining is that it allows the users to keep the same selections regardless the app they are viewing.
In the Country-Region case, let's say I see Dashboard.qvw where I see an overview for the company, but then I select year 2016 and country Spain and click on "Detail", which opens Detail.qvw with Year = 2016 and Country = Spain already selected.
Document chaining works well with IE Plugin as well as Ajax interface.
Miguel
.png "Miguel_Angel_Baeyens"){kind=avatar}
