Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Section Access Being Ignored

Help. I have a major problem. I have a SECTION ACCESS which is not being applied on the server. I cannot deploy this application without this. I have several other applications with similar SECTION ACCESS that are working fine but not this one.

Snippets (cannot provide actual QVW due to proprietary info.):

SECTION ACCESS

LOAD * INLINE [

    ACCESS, NTNAME, CLIENT_ID

    ADMIN, CRENT\AMACDONALD,

    ADMIN, CRENT\JASONP,

    ADMIN, CRENT\ROBROBIN,

    ADMIN, SCE\SALLEN,

    ADMIN, SCE\DNELSON,

    ADMIN, SCE\EWHITMORE,

    ADMIN, CRENT\QLIKMASTER,

    ADMIN, CRENT\QLIKUSER,

    USER, "SCE\!SCEALL",

   USER, "CRENT\ZCU1", "afc12e33ce244ea03632ee0299000eca",

];

Section Application;

Settings

     Document

          Server tab - checked: Filter Access Point Document List Based on Section Access

          Security tab - checked: reduce data, allow export and Admin override security

          Openingn tab - checked: initial data reduction based on Section Access

     QEMC

          Reduce tab - reduction method / reduce by field value (standard setting)

However, when I log in as userid CRENT\ZCU1 I am still seeing ALL values for CLIENT_ID:

ZCU1.jpg

What am I missing!?!?!?!?!?

Sue

1 Solution

Accepted Solutions
Not applicable
Author

Found!!! The VALUE of the security-related field has to be all upper case, as well as the field name.

So in the data load, added upper(CLIENT_ID) and in the security, converted the key to upper case.

Tada...

Thanks for all the suggestions, folks.

View solution in original post

6 Replies
alexpanjhc
Specialist
Specialist

USER, "CRENT\ZCU1", "afc12e33ce244ea03632ee0299000eca",

try to remove the last comma?

daveamz
Partner - Creator III
Partner - Creator III

Hello Sue,

     Before log in as userid CRENT\ZCU1 close all instances of QV.

David

Not applicable
Author

No dice on either of these ideas. 😞

alexpanjhc
Specialist
Specialist

just out of curiosity, why do you have double quotes on this user but not others? the client id too?

Not applicable
Author

I've tried it with/without quotes. No difference. Also tried with/without strict exclusion. Having strict exclusion checked locked me out of the app altogether. Next thing I'm going to try is converting the security VALUE to all caps. I didn't think that was necessary but maybe it is!?!?!?

Not applicable
Author

Found!!! The VALUE of the security-related field has to be all upper case, as well as the field name.

So in the data load, added upper(CLIENT_ID) and in the security, converted the key to upper case.

Tada...

Thanks for all the suggestions, folks.