Section access issue in Qlik Sense

[nakuldev]

Hi All,

After reloading the section access script, I am getting  the following error, "Access was denied after reload. Check that the user that reloads the script is included in the section access part of the script." 

I already added my details, however, QS is showing same error.

Below is the section access I added:

Section Access;

SECURITY:
LOAD * inline [
ACCESS,           USERID,            RESTRICTION
  USER,      DOMAIN\F12345D,          *
  USER,      INTERNAL\SA_SCHEDULER, *
];

Concatenate(SECURITY)
LOAD
Upper(trim("Access")) as ACCESS,
Upper(trim("UserID")) as USERID,
Upper(trim(Region)) as RESTRICTION
FROM [lib://AttachedFiles/ User List.xlsx]
(ooxml, embedded labels, table is [SECURITY]);

Star is '*';

Section Application;

Thanks

Nakul

[JuanGerardo]

Hi @nakuldev, add your user with ADMIN role to be able to open the script:

Section Access;

SECURITY:
LOAD * inline [
ACCESS,           USERID,            RESTRICTION
  ADMIN,      DOMAIN\F12345D,          *
  USER,      INTERNAL\SA_SCHEDULER, *
];

JG

[nakuldev]

Hi Juan,

Initially I tried my user access with ADMIN only, however few suggested to use USER,so I changed it.

However, the issue still remains.

Thanks

Nakul

[JuanGerardo]

Maybe the RESTRICTION field is not well implemented, for example, is also using uppercase in your fact data?

If you comment your section access (lines in bold), can you select one user from SECURITY table (not using *) and see data?

//Section Access;

SECURITY:
LOAD * inline [
ACCESS,           USERID,            RESTRICTION
  USER,      DOMAIN\F12345D,          *
  USER,      INTERNAL\SA_SCHEDULER, *
];

Concatenate(SECURITY)
LOAD
Upper(trim("Access")) as ACCESS,
Upper(trim("UserID")) as USERID,
Upper(trim(Region)) as RESTRICTION
FROM [lib://AttachedFiles/ User List.xlsx]
(ooxml, embedded labels, table is [SECURITY]);

//Star is '*';

//Section Application;

JG

[JuanGerardo]

BTW, the INTERNAL\SA_SCHEDULER user should also be added as ADMIN. Have you tried that?

JG

[nakuldev · Accepted solution]

Hi Juan,

It's resolved now. The issue was with Domain, client provided me with new domain which resolved the issue.

Thanks

Nakul