Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Section access not working

Hello everyone,

I have an application which contains data about several zones (let's say countries).

I have inserted a section access at the beginning of the script so each user see only the data about the countries he is entitled to see.

section access;

load * inline [

ACCESS, USERID,  PASSWORD , country

ADMIN, ADMIN, ADMIN,

USER, laura, laura, France

];

Section application;

When I reload, save and reopen my application using the laura "account" (I mean user and password laura), I still see the data for every countries...

Instead of the section access, I have tried to just insert a table :

test:

// section access;

load * inline [

ACCESS, USERID,  PASSWORD , country

ADMIN, ADMIN, ADMIN,

USER, laura, laura, France

];

so I get a new table with the fields access, userid, password and country. And when in my application, I filter on the userid field (on "laura"), the filtering works well (I do see only the information about France).

What is wrong with my section access ?

Thank you for your help

Laura

1 Solution

Accepted Solutions
simenkg
Specialist
Specialist

Under Settings - Document Settings - Opening:

Check the checkbox named : Initial data reduction based on Section Access

All field names in section access needs to be UPPERCASE. change country to COUNTRY and duplicate the country field in you data model with the name COUNTRY.

View solution in original post

3 Replies
simenkg
Specialist
Specialist

Under Settings - Document Settings - Opening:

Check the checkbox named : Initial data reduction based on Section Access

All field names in section access needs to be UPPERCASE. change country to COUNTRY and duplicate the country field in you data model with the name COUNTRY.

Not applicable
Author

Thank you Simen !!

awhitfield
Partner - Champion
Partner - Champion

Hi,

you also wan to tick "Strict Exclusion"

“Strict Exclusion”

Access to the document will be denied whenever the field values in the section access

reduction fields lack matches in their corresponding section application field.

Having this option unselected will mean that if QlikView can’t find a match to reduce

data, all data in the document will be visible on USER level. However, ADMIN will

always be able to see all data, regardless of the reduction. Best practice is to use strict

exclusion to avoid unwanted access to the QlikView document.