Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
nikhilgarg
Specialist II
Specialist II

Section Access prob

Hey,

I applied the section access in my application as:

LOAD * Inline [

ACCESS , USERID , PASSWORD

ADMIN, ADMIN, ADMIN

SASH,SASH,SASH

LORNE,LORNE,LORNE

];

Section Application;

But when i opened it again, and provide the userid and password as SASH, i am getting all data rather than SASH data only.

Where am i wrong?

Thanks

15 Replies
antoniotiman
Master III
Master III

Hi,

Your Section Access simply means only  3 Users gain access to the document whitout any restriction.

Could You explain 'rather than SASH data only' ?

Have You any Conditional Expression like QVUser()='SASH' in Sheet or Objects ?

nikhilgarg
Specialist II
Specialist II
Author

Yes,

I did the same way

jonathandienst
Partner - Champion III
Partner - Champion III

For data reduction, you will need to specify in the load some sort of key value that exists outside of Section access. Something like this:

Data:

LOAD ....

         Upper(IDDiv) As DIVCODE,

          ....

Section Access;

LOAD * Inline [

ACCESS , USERID , PASSWORD, DIVCODE

ADMIN, ADMIN, ADMIN,

USER,SASH,SASH, 123

USER,LORNE,LORNE, 456

];

Section Application;

ADMIN can access all, SASH can access 123, LORNE can access 456

Update to use a relevant key for your application.

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
daniel_kusiak
Creator II
Creator II

I made a test for:

Section Access;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD, OMIT

    ADMIN, ADMIN, ADMIN,

    USER, DANIEL, DANIEL, UNIT NAME

];

SECTION Application;

As a ADMIN i can see all data. As a Daniel i see all data without UNIT NAME

In load script i have alias unit_n as [Unit Name]. In Section application i've used name after alias.

jonathandienst
Partner - Champion III
Partner - Champion III

OMIT is for column security, so you can hide a specific column. Data reduction is for row security, so you can hide data rows completely. You can combine both types of security into a single model if required.

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
Gabriel
Partner - Specialist III
Partner - Specialist III

Hi,

Reading your explanations of the issue, it sounds to me that you want to do Dynamic Data Reduction.

If this is the case, your Section Access script has no Reduction Field.

You have to reduce user's access based on one field. Page 9 of the file attached by awhitfield talks about Reduction Field

Hope this help