Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have a scenario where we intend to use Section Access on a hierarchy table.
To illustrate the issue I would use the below example -
Imagine a data table like below -
Continent | Country | City |
North America | Canada | Toronto |
North America | Canada | Vancouver |
North America | US | Los Angeles |
North America | US | New York |
Europe | Germany | Munich |
Europe | Germany | Berlin |
Europe | France | Paris |
Europe | France | Marseille |
Europe | Italy | Rome |
Europe | Italy | Milan |
Asia | China | Shanghai |
Asia | China | Beijing |
Asia | India | Delhi |
Asia | India | Mumbai |
Asia | Japan | Tokyo |
Asia | Japan | Osaka |
Following is the Section Access Table we are using -
ACCESS | USERID | Continent | Country | City |
ADMIN | User 1 | North America | US | New York |
ADMIN | User 2 | Asia | India | Delhi |
ADMIN | User 3 |
| US |
|
ADMIN | User 3 |
|
| Delhi |
User 1 has perfect access restricted only to New York.
User 2 has perfect access restricted only to Delhi.
User 3 wants access to all cities in US along with access to Delhi. How can we achieve this?
We get access denied all values on the above case for User 3.
Can you replace * instead of null or space ?
Given your Section Access table all the users should be able to see all the data since they all have ADMIN level access. I'm pretty sure you've not posted the section access table you really use.
Note, ALL field names and ALL field values in the Section Access table should be in capital letters. The corresponding field names and values in your data model should also be in capital letters. And unless you have a City that exists in multiple Countries I advice that you always fill the Country and Continent columns in the section access table as well.
Tried that and populated all the list of values under a dummy user ID (as * only uses previously listed values). But the script fails and shows all values instead.
You are right about that, it's just an example to demonstrate a similar scenario we are facing. And we do use ALL field values in upper case for Section Access Table.
Also Blanks ONLY work when ACCESS level is "ADMIN" in Qlik Sense. With ACCESS as "USER" we "get Access Denied". ACCESS as ADMIN works for Qlikview, however in Qlik Sense it doesn't behave the same way as it does in Qlikview Section Access. I recently learnt that from Qlik.