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

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Peony
Creator III
Creator III

Issue with access to the dashboard pages via section access

Hi all.
Hope the power of community will help me to understand what am I doing wrong regarding access to the dashboard pages.🙏

I have a dashboard with 3 pages: A and B. Each page should be available to the certain list of users. Some of the users  may have an access to the only one page, others may have access to the both pages. Later there will be more pages and access combinations. 

My code is next:

Page:
Load * Inline [
PAGE
A
B
];

TEMPSectionAccess:
Load
ACCESS,
Upper(USERID) as USERID,
Upper(PAGE) as PAGE
From [Section Access.xlsx](ooxml, embedded labels, table is Sheet1);

Section Access;
SectionAccessTab:
Load
ACCESS,
USERID,
PAGE
Resident TEMPSectionAccess;

Section Application;

Drop Table TEMPSectionAccess;

Than to each page of the dashboard I applied next show condition:
For Page A     If(Match(PAGE,'A'),1,0)
For Page B    If(Match(PAGE,'B'),1,0)

Data that is taken from the Excel file is looks like this

Peony_0-1751627175855.png


When User1 login into the dashboard, this user see only page A. But when user User2 opens the dashboard, he see no pages at all. But I expected he would see both pages. And I can't understand why. 😢

 

 

Labels (2)
1 Solution

Accepted Solutions
marcus_sommer

The reason is your match-query against PAGE which contained no explicit aggregation which means that implicitly only() is taken and User2 has two different values which results in NULL.

AFAIK it's not mandatory necessary to apply such expression else using directly the fields. Here an example as starting point: Sheet level access - Qlik Community - 1482009

View solution in original post

2 Replies
marcus_sommer

The reason is your match-query against PAGE which contained no explicit aggregation which means that implicitly only() is taken and User2 has two different values which results in NULL.

AFAIK it's not mandatory necessary to apply such expression else using directly the fields. Here an example as starting point: Sheet level access - Qlik Community - 1482009

Peony
Creator III
Creator III
Author

@marcus_sommer Thank you for the answer and the link. Now my issue is solved.