Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
Larissa93
Partner - Contributor
Partner - Contributor

Set Analysis ignores Section Access?

Hi,

we have the following issue: we have a field USERNAME which is used in the SectionAccess table to restrict user access to the data of a specific user.

In general, it works fine. However, if we use the field USERNAME in a dimension together with the following Set Analysis expression: {$<VALUE={1}>} USERNAME , the resulting dimension values contain ALL usernames including those which should be hidden by Section Access.

The version we use is Qlik Sense Enterprise on Windows August 2023 Patch 6. We could not reproduce the behavior using Qlik Sense Enterprise on Windows November 2021 Patch 4.

The following loadscript provides a minimal working example, results are attached:

Data:
Load * Inline [
USERNAME,VALUE
Abc,1
Abc,2
Def,3
Ghi,4
];
 
Data2:
Load
    USERNAME,
    1 As VALUE2
Resident Data;
 
AccessTable:
Load Distinct * Inline [
    ACCESS,USERID,USERNAME
    ADMIN,INTERNAL\SA_SCHEDULER,*
    USER,*,Abc
];
 
Section Access;
SectionAccess:
Load * Resident AccessTable;
Section Application;
Drop Table AccessTable;

 

Is this a known issue and when will there be a fix?

Labels (1)
3 Replies
Or
MVP
MVP

I wasn't able to replicate this in May 2023, but regardless I'd suggest opening a Support ticket to make sure you both get the latest information on whether this is a known issue, and if it isn't, make sure it's filed as a bug and addressed.

vincent_ardiet_
Specialist
Specialist

Section access values are only working in uppercase if I'm not wrong. Try with first with uppercase to see if this is solving it.

Larissa93
Partner - Contributor
Partner - Contributor
Author

Thanks for the hint but it doesn't solve it. And the Section Access is actually working fine except for this special case with the set analysis