Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
How can we implement Section access in Qliksense?
Pls Suggest
Hello Abhay,
Refer below link for Section Access.
Managing security with section access ‒ Qlik Sense
Don't forget to add internal user of Scheduler in list of user as ADMIN.(internal\sa_scheduler).
I hope this is helpful.
Regards,
Shraddha.
Hi Abhay,
The Section Access code in Qliksense is same as Qlikview. Check below link for more details.
Managing security with section access ‒ Qlik Sense
Regards,
Jagan.
I'm curious why you need to do this?
HI Abhay,
Please let me know your requirement I will write the logic for you..
as a sample please find my logic for cost centre section access restriction to the cost centre managers:
TMP1:
LOAD
OPD,
UPPER("Access") AS ACCESS,
UPPER("Userid") AS USERID,
Fullname
FROM [lib://QS_Cost_Center (opd_f29121)/Userlist.xlsx]
(ooxml, embedded labels, table is [Master OPD List]);
TMP2:
Load
ACCESS,
(OPD&USERID) AS USERID,
Fullname
RESIDENT TMP1;
join
LOAD
UPPER("Cost Centre Number") as [COST CENTRE],
"Cost Centre Manager" AS Fullname
FROM [lib://QS_Cost_Center (opd_f29121)/Copy of Cost Centre Hierarchy - CURRENT 22.06.16.xlsx]
(ooxml, embedded labels, table is [SAP Hierarchy]);
TMP3:
LOAD
ACCESS,USERID,[COST CENTRE]
RESIDENT TMP2;
Concatenate
LOAD * inline [
ACCESS, USERID,COST CENTRE
USER, OPD\F29121,*
USER, OPD\EVANSP1,*
USER, OPD\KENNYS,*
USER, OPD\F22020,*
USER, OPD\SMOULD1,*
USER, OPD\KINSEC1,*
USER, OPD\CSTRAN1,*
USER, OPD\F26075,*
USER, OPD\F21462,*
USER, OPD\F28159,*
USER, OPD\F27245,*
USER, OPD\F25301,*
USER, OPD\F29591,*
];
star is *;
section access;
Load * Resident TMP3;
section Application;
drop table TMP1;
drop table TMP2;
drop table TMP3;
The principle is the same, but there is a difference in the system fields that you apply in Qlik Sense vs QlikView section access.
rittermd are you referring to the usage of internal\sa_scheduler? Or that it needs to be an ADMIN?
internal\sa_scheduler is the user used by the reload engine to access the app during reload.
A person with ADMIN privileges has access to all data in the app. For this reason the reloading user should be an ADMIN user. The online help unfortunately refers to the internal\sa_scheduler with USER level ACCESS. This will be corrected in coming releases of help, to clarify that ACCESS must be set as ADMIN.