topic Re: Section Access in QlikView

Section Access

kev6brown — Wed, 05 Jun 2024 12:34:32 GMT

I have the following section access script in my hidden script -

Section Access;

LOAD * INLINE [
ACCESS, NTNAME, OMIT, SLRLEVEL8, SLRLEVEL7
ADMIN, DOMAIN\USER1, *, *, *
ADMIN, DOMAIN\USER2, *, *, EMERGENCY DENTAL SERVICE
ADMIN, DOMAIN\USER3, NHSNO, *, EMERGENCY DENTAL SERVICE
ADMIN, DOMAIN\USER3, NHSNO, *, SPECIAL CARE DENTAL SERVICE
];

Section Application;

When opening the dashboard my log in - DOMAIN\USER1, I can only see EMERGENCY DENTAL SERVICE and SPECIAL CARE DENTAL SERVICE and cannot see NHSNO.

Why is this happening? I should be able to see everything

Thanks

Kev

Re: Section Access

TauseefKhan — Wed, 05 Jun 2024 13:53:32 GMT

Hi @kev6brown,

This could be because:

• The * in SLRLEVEL7 is not being interpreted as "all data". Instead, it's being treated as a literal value.

• There might be a conflict with other user settings, especially if multiple entries for the same user exist with different access rights.

• There could be an issue with how the data model is set up, affecting the data reduction process.

***Hope this resolve your issue.
If the issue is solved please mark the answer with Accept as Solution & like it.***

Re: Section Access

kev6brown — Wed, 05 Jun 2024 14:10:09 GMT

Any idea how I change it so it does interpret it as "All Data"?

Re: Section Access

TauseefKhan — Wed, 05 Jun 2024 14:21:56 GMT

* wildcard in Section Access is interpreted as "All Data," you need to make sure that the reduction fields (SLRLEVEL8, SLRLEVEL7, etc.) are properly linked to your data model.

Re: Section Access

kev6brown — Thu, 06 Jun 2024 08:14:49 GMT

I've removed SLRLEVEL7 and anything in OMIT. So just SLRLEVEL8 is being reduced, however it is still not working, even though it does link in the data model

Re: Section Access

BrunPierre — Thu, 06 Jun 2024 08:59:43 GMT

DOMAIN\USER1 has a "*" added, indicating that all fields listed in OMIT will be hidden.

If you want this user to see the field NHSNO, leave the OMIT value blank.

Re: Section Access

kev6brown — Thu, 06 Jun 2024 09:08:40 GMT

I have removed OMIT from the table so it now looks like -

Section Access;

Access:

LOAD * INLINE [

ACCESS, NTNAME, SLRLEVEL8

ADMIN, DOMAIN\USER1, *

ADMIN, DOMAIN\USER2, CARER HEALTH TEAM

ADMIN, DOMAIN\USER3, OVERNIGHT SERVICE COASTAL

];

Section Application;

I'm now seeing CARER HEALTH TEAM and OVERNIGHT SERVICE COASTAL when i should see everything

Re: Section Access

BrunPierre — Thu, 06 Jun 2024 09:35:17 GMT

In Section Access, the "*" character in a reducing field represents only the values listed in Section Access, not any additional values in the data.

Star is *;

Section Access;

Access:
...

Re: Section Access

kev6brown — Thu, 06 Jun 2024 09:36:24 GMT

Ok that makes sense, so if I want to be able to see all values do I just leave SLRLEVEL8 blank for me?

Re: Section Access

BrunPierre — Thu, 06 Jun 2024 09:47:27 GMT

This thread has multiple scenarios: Managing data security with Section Access

Re: Section Access

marcus_sommer — Thu, 06 Jun 2024 12:10:33 GMT

A quite simple approach to include/exclude all values with a wildcard is to list these values within section access, maybe with something like:

SA:
load 'USER' as ACCESS, 'NONE' as NTNAME,
text(fieldvalue('REDUCTION', recno())) as REDUCTION
autogenerate fieldvaluecount('REDUCTION');

concatenate(SA) load .... from YourSectionAccess;

If there are only a few REDUCTION values they might be simply listed in an inline-statement but like shown such listing against a dummy-user could be also retrieved from the data-set or loaded from a prepared qvd.

Beside this - automatically applied looping and merging approaches might be also used to define all wanted accesses and therefore avoiding the wildcard-stuff.