topic Re: Qliksense Section Access Script in App Development

Qliksense Section Access Script

sharu055 — Wed, 19 Feb 2025 16:43:22 GMT

I am migrating my qlikview app to qliksense, in qlikview we use the below script for section access to provide access to users. If i use the same script in qliksense its not working. Please help in writing qliksense script for section access. Thanks in advance.

Qlikview Script:

Section Access;

LOAD Upper(ACCESS) as ACCESS,
NTNAME ,
Upper(PERMISSION) as PERMISSION1

FROM [../Section Access.xlsx]

(ooxml, embedded labels, table is Section_Access);

Section Application;

Data example:

ACCESS	NTNAME	PERMISSION
ADMIN	Red	*
ADMIN	Orange	*
User	Green	Green
User	Green	White
User	Green	Black
User	Black	Black

Re: Qliksense Section Access Script

Chanty4u — Wed, 19 Feb 2025 17:58:14 GMT

Code looks ok but you have to change your from path in qliksense it's quite different than qlikview

Section Access;

LOAD

UPPER(ACCESS) as ACCESS,

NTNAME,

UPPER(PERMISSION) as PERMISSION1

FROM [lib://YourDataConnection/Section Access.xlsx]

(ooxml, embedded labels, table is Section_Access);

Section Application;

Re: Qliksense Section Access Script

sharu055 — Thu, 20 Feb 2025 10:29:15 GMT

Yes, I used the proper path for qliksense to fetch the data, after refresh i am getting the below popup. I am into Admin and permission is *. Not sure why i am getting below popup, Its in Dev not moved to UAT.

Re: Qliksense Section Access Script

simsa — Sat, 22 Feb 2025 14:03:02 GMT

In a text and Image viz- just type out osuser() and check your userid-
For instance, if directory is XYZ and user id is ABC- then username will be XYZ\ABC

I hope the format that you have provided is correct

Re: Qliksense Section Access Script

Ravi1212 — Sun, 23 Feb 2025 17:39:08 GMT

Hello @sharu055 ,
You can refer below script and considerations ==>

Qlik Sense Section Access Script (Equivalent to QlikView Logic)
Section Access Implementation

Section Access;

// Load the security table (Qlik Sense is case-sensitive)
LOAD
Upper(ACCESS) as ACCESS, // Should be either "ADMIN" or "USER"
Upper(NTNAME) as USERID, // Must align exactly with the Qlik Sense login (case-sensitive)
Upper(PERMISSION) as PERMISSIONS // The field name should be "PERMISSIONS" (not singular)
FROM [lib://YourFolder/Section_Access.xlsx]
(ooxml, embedded labels, table is Section_Access);

Section Application;

// Your main data model starts here...

== Key Differences Between QlikView & Qlik Sense ==

Field Naming Conventions:
Instead of NTNAME, Qlik Sense expects USERID, which should precisely match the user’s login (e.g., DOMAIN\Ravi or an email address).
The field PERMISSIONS must be used instead of PERMISSION1 (note the plural form).
Case Sensitivity Considerations:
User logins in Qlik Sense are case-sensitive.
To prevent mismatches, use Upper() to standardize usernames if they are stored in uppercase.

Permission Formatting:
If a user has access to multiple permissions, separate them using semicolons (;).

ACCESS USERID PERMISSIONS
ADMIN DOMAIN\Red *
ADMIN DOMAIN\Orange *
USER DOMAIN\Green Green;White;Black
USER DOMAIN\Black Black

Essential Qlik Sense Considerations :

User Authentication:
Ensure that users log into Qlik Sense through an identity provider (e.g., Active Directory, OIDC) that corresponds to the format used in USERID.

Restricting Sheet Access:
After reloading, control sheet-level access by right-clicking the sheet > Properties > Security settings.

Data Reduction:
If you need to limit access to specific rows in the dataset, add an OMIT field in the Section Access table.

Troubleshooting & Common Issues ==>
"No Data Available" Error: Ensure that USERID exactly matches the logged-in user’s identity. You can confirm this by checking =OSUser() in a text object.

Permission Issues: Use * for admin users to grant unrestricted access.

Reloading Issues: Always test the script with a user who has both Section Access rights and proper QMC security permissions.

Re: Qliksense Section Access Script

ali_hijazi — Mon, 24 Feb 2025 07:49:55 GMT

In QlikSense the NTNAME is replaced by USERID
so you need at least two columns in the section access:
ACCESS: which takes either ADMIN or USER
USERID: in the form of DOMAIN\USERNAME