Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

OMIT in Section Access

I'm playing around with section access at the moment with a view to implement it in a document for a client.

I'm testing to see how the OMIT field works in section access but I cant seem to get it to to work.

I've created 2 users one is ADMIN one is USER which as an OMIT on a field in the script (a cost column).

The document requests login and password when opening but when logging in as the USER the omitted field is still visible in the document where it is used.

Am I doing something wrong?

Labels (1)
1 Solution

Accepted Solutions
Not applicable
Author

Hi,

Maybe -

Check the selected option  “Settings” -> “Document Properties” -> “Opening” ->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.

View solution in original post

2 Replies
Not applicable
Author

Hi,

Maybe -

Check the selected option  “Settings” -> “Document Properties” -> “Opening” ->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.

Not applicable
Author

That worked!

Thanks for that. This is just what I'm looking for