Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi, QlikView community,
I’m currently working on a QlikView app where I need to implement section access based on two fields: REGION and STORE. However, I have a unique situation and I’m seeking advice on how to solve it:
Data Model:
• I have two tables in my data model: Fact with fields like (saleid, customer_name, region, etc) and Annotations with fields like (region, store, category, etc). The annotations table is mainly used to map annotations to the fact table but is not joined to it. It is a stand-alone table
• I use an excel file with a table Authorization where I have fields like (ACCESS, NTNAME, SAUSER)
Finally after the section access, I have an inline table that maps SAUSER to region where my section access is currently applied to.
Section Access Requirements:
By default, all users in a region should have access to all stores in that region, but there is now a new store in one of the regions, and only specific users in that region should have access to it.
Challenges:
I need advice on how to set up section access to handle this exception. How can I configure the section access table to grant access to all stores in the region except for the newly opened one, while allowing specific users to access the new store?
Any guidance or examples on how to approach this would be greatly appreciated!
It sounds as if you would need generic keys. Take a look at
https://community.qlik.com/t5/Design/Basics-for-complex-authorization/ba-p/1465872
Generic keys and other advanced scripting methods are described in my book "Qlik according to HIC".
As HIC is saying or you apply logic on and transform your inline table into a table that maps your SAUSER to STORE and not to REGION.
It sounds as if you would need generic keys. Take a look at
https://community.qlik.com/t5/Design/Basics-for-complex-authorization/ba-p/1465872
Generic keys and other advanced scripting methods are described in my book "Qlik according to HIC".
As HIC is saying or you apply logic on and transform your inline table into a table that maps your SAUSER to STORE and not to REGION.