Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I need to make a dashboard for our stores. Our stores are divided by something like a region. To make it easier to explain I’ll use region. There are more than 15 regions. For each region there's one user who will access QlikView bij the accesspoint.
The dashboard should look like this:
I thought to restrict this with section access.
For the testing I'll user USERID and PASSWORD but later on I'll change this to NTNAME.
I've tried the basic selection access based on profile. In the section access part I'll add the profile and in the selection application I'll connect this profile to the field Store_region to restrict the data. This works for sheet 2, but the data in sheet 1 is also restricted (as I've expected).
I saw that there's also a solution to use sheet access. to set which user can access which sheet in the selection application and with an conditional on the sheet. But this means that I’ll need to make more than 15 sheets. That's okay for once, but seems difficult to maintain.
What's the best practice to make this?
There's an extra difficulty that the manager also wishes that the regions on sheet 2 can compare their performance (based on indexes) with the other regions. If you have a solution for this as well this would be nice, otherwise I’ll add this comparison to sheet 1.
Thanks in Advance.
Hi Astrid,
You may want to have a look into document chaining, as suggested by Henric in his blog post:
http://community.qlik.com/blogs/qlikviewdesignblog/2014/06/09/methods-for-data-reduction
http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access
Introduction to Section Access
Cited from the first:
"It is difficult to achieve aggregation-level access within one single application, so it is better to solve this problem using two applications: One with detailed data that you reduce using a reducing field, and a second unreduced with aggregated data for all countries."
Hi Astrid,
You may want to have a look into document chaining, as suggested by Henric in his blog post:
http://community.qlik.com/blogs/qlikviewdesignblog/2014/06/09/methods-for-data-reduction
http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access
Introduction to Section Access
Cited from the first:
"It is difficult to achieve aggregation-level access within one single application, so it is better to solve this problem using two applications: One with detailed data that you reduce using a reducing field, and a second unreduced with aggregated data for all countries."
Thank you, I'll look into this!