Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Section Access

Hi All,

I've been trying to implement section access in my application but have found an issue I couldn't resolve.

I've got two scripts I'm playing with. The first one below works perfectly fine:

LOAD * inline [
ID
1A
1B
1C
];

Section Access;
LOAD * inline [
ACCESS,  NTNAME, ID
USER, name1, 1A
USER, name2, 1A
USER, name2, 1B
]
;
Section Application;

I have checked "initial selection based on section access" in document properties.

With this, when I log in as user 2, I see 1A and 1B and don't see 1C which is great.

Try something different:



LOAD * inline [
ID
1Aus
1Bus
1Cus
];

Section Access;
LOAD * inline [
ACCESS,  NTNAME, ID
USER, name1, 1Aus
USER, name2, 1Aus
USER, name2, 1Bus
]
;
Section Application;

And section access doesn't work. I didn't think there would be any difference in the two examples but I'm getting different behaviour.

Thanks a lot

1 Solution

Accepted Solutions
Bill_Britt
Former Employee
Former Employee

OK, got it working and you are right the one below doesn't work.  However, one of the requirement for section access is everything has to be in upper case. So, If you change everything to upper case it works. See attached and use your login name1 etc

LOAD * inline [
ID
1Aus
1Bus
1Cus
];

Section Access;
LOAD * inline [
ACCESS,  NTNAME, ID
USER, name1, 1Aus
USER, name2, 1Aus
USER, name2, 1Bus
]
;
Section Application;

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.

View solution in original post

7 Replies
Bill_Britt
Former Employee
Former Employee

Hi,

Take a look at the attach and see if that will help you.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
sinanozdemir
Specialist III
Specialist III

Try this:

Capture.PNG

Bill_Britt
Former Employee
Former Employee

OK, got it working and you are right the one below doesn't work.  However, one of the requirement for section access is everything has to be in upper case. So, If you change everything to upper case it works. See attached and use your login name1 etc

LOAD * inline [
ID
1Aus
1Bus
1Cus
];

Section Access;
LOAD * inline [
ACCESS,  NTNAME, ID
USER, name1, 1Aus
USER, name2, 1Aus
USER, name2, 1Bus
]
;
Section Application;

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
Not applicable
Author

Fantastic.

This isn't mentioned in the documentation as far as I am aware. Thanks a lot. But this also means I have to create a new field in my data model with the values in uppercase.

mohammadkhatimi
Partner - Specialist
Partner - Specialist

No just write function upper(fieldname)  as Fieldname it will works....

Bill_Britt
Former Employee
Former Employee

HI,

That is correct, but hard to do with an inline load.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
Bill_Britt
Former Employee
Former Employee

Hi,

If you look at the QlikView Reference manual you will find:

All the fields listed in Load or Select statements in the section access must be written in UPPER CASE. Any

field name containing lower case letters in the database should be converted to upper case using the upper

function, see upper(textexpression) (page 335), before being read by the Load or Select statement. However

the user ID and the password entered by the end-user opening the QlikView documents are case insensitive.

In the 11.20 SR12 manual it is on page 419.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.