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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
ireshaimali890
Contributor II
Contributor II

Qlik Sense Enterprise Access

I cannot give access to a new user. When I create the Section Access file and upload the USERID, ACCESS, and KEY columns in a Notepad file and link the path to the app, it works for some apps. I did the same steps for a new app, and I was able to give access to a new user, but for some other apps it does not work, even though the structure in Notepad file is the same. Why is this happening? Any reasons? (Qlik Sense Enterprise Access)

in app script:

Section Access;
LOAD
"USERID",
"ACCESS",
KEY
FROM [path.txt]
(txt, codepage is 28591, embedded labels, delimiter is ',', msq);

Section Application;
Data_Deduction:
Load * Inline [
KEY,COMPANY_CODE
*,*
2,2
3,3
4,4
5,5
6,6
];

Company_SA_Master:
Load * Inline [
"Legal Entity",COMPANY_CODE
832,2
1332,3
872,4
834,5
1632,6
];

in note pad,

"DOMAIN\user1",ADMIN,*
"DOMAIN\user2",ADMIN,*
"DOMAIN\user3",USER,*
"DOMAIN\user4",USER,*
"DOMAIN\user5",USER,*
"DOMAIN\user6",USER,*
"DOMAIN\user7",USER,*
"DOMAIN\user8",USER,*
"DOMAIN\user9",USER,*
"DOMAIN\user10",USER,2
"DOMAIN\user11",USER,3
"DOMAIN\user12",USER,4
"DOMAIN\user13",USER,5
"DOMAIN\user14",USER,6
"DOMAIN\user15",USER,2
"DOMAIN\user16",USER,3
"DOMAIN\user17",USER,5
"DOMAIN\user18",USER,2
"DOMAIN\user19",USER,3
"DOMAIN\user20",USER,5
"DOMAIN\user21",USER,2
"DOMAIN\user22",USER,3
"DOMAIN\user23",USER,5
"DOMAIN\user24",USER,2
"DOMAIN\user25",USER,3
"DOMAIN\user26",USER,5
"DOMAIN\user27",USER,2
"DOMAIN\user28",USER,3
"DOMAIN\user29",USER,5
"DOMAIN\user30",USER,4
"DOMAIN\user31",USER,4
"DOMAIN\user32",USER,4
"DOMAIN\user33",USER,4
"DOMAIN\user34",USER,*
"DOMAIN\user35",USER,2
"DOMAIN\user36",USER,3
"DOMAIN\user37",USER,5
"DOMAIN\user38",USER,2
"DOMAIN\user39",USER,3
"DOMAIN\user40",USER,5
"DOMAIN\user41",USER,2
"DOMAIN\user42",USER,3
"DOMAIN\user43",USER,5
"DOMAIN\user44",USER,2
"DOMAIN\user45",USER,3
"DOMAIN\user46",USER,5
"DOMAIN\user47",USER,4
"DOMAIN\user48",USER,4
"DOMAIN\user49",USER,4
"DOMAIN\user50",USER,1
"DOMAIN\user51",USER,2
"DOMAIN\user52",USER,3
"DOMAIN\user53",USER,1
"DOMAIN\user54",USER,2
"DOMAIN\user55",USER,3
"DOMAIN\user56",USER,1
"DOMAIN\user57",USER,2
"DOMAIN\user58",USER,3
"DOMAIN\user59",USER,4
"DOMAIN\user60",USER,4
"DOMAIN\user61",USER,*

 

 

Labels (1)
3 Replies
rubenmarin

Hi, my first guess would be checking that the values loaded in the KEY field are also loaded in the app, maybe those other apps are using other data sources and none of the KEY assigned to the user are being loaded in those apps.

Nagaraju_KCS
Specialist III
Specialist III

It may cause.

1. In your app's load script, ensure you use the Upper() function on the KEY field in both the Section Access and the Section Application sections to should a perfect match.

2. If you use a binary load, ensure the Section Access is defined only once in the final application, and that the binary load is placed before the Section Access; block.

like below:

Section Access;
LOAD ACCESS, UPPER(USERID) as USERID, UPPER(KEY_FIELD) as KEY_FIELD
FROM file_path;

Section Application;
LOAD *, UPPER(KEY_FIELD) as KEY_FIELD
FROM Main_Table;

 

rubenmarin

You can also try changing * to ALL in section access, and load KEY-COMPANY_CODE relation as:

Data_Deduction:
Load * Inline [
KEY,COMPANY_CODE
2,2
3,3
4,4
5,5
6,6
];

Concatenate (Data_Deduction)
LOAD
  'ALL' as KEY,
  COMPANY_CODE
Resident Data_Deduction;