Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi There
Something is not working correctly in my section access.
My qlikview user is peterz.
when reloading with the below section access applied.
my user peterz can only see CODE_2 A12.
According to my script, peterz must have access to all CODE_2
it seems as if all other users can also only see A12
for now it seems like kevin can see only A12 CODE_2s linked to COST_CENTRE 2101.
he needs to see all CODE_2s for COST_CENTRE 2101
Your assistance is appreciated.
Section Access;
LOAD * INLINE [
ACCESS, NTNAME, COST_CENTRE, CODE_2
USER,DOMAINNAME\Johna , *, A12
USER, domainname\peterz ,*, *
USER, domainname\paulo ,*,*
USER, domainname\kevinw , 2101,*
];
Section Application;
OK can you please post your section application code...
FYI:
section will control the access to the document , data access will be taken care in section application code, we are miss that here, please post that.
Hi,
If you want to give domainname\peterz all access change it ACCESS from USER to ADMIN.
Regards
The position of the reduction field does not matter. However, if you have multiple reduction fields there is an increased risk that you have not predicted the outcome correctly.
Also keep in mind that the reduction values must be in upper case, in both the reduction field in section access table and in the data table.
Hi Toni
From What I have read on previous posts, the Lower case and upper case make a difference when loading from QVD... There are many users so im just afraid how long it will take for me to change to upper case... Do you think it will definitely have an impact?
Thank you I was not aware what * meant I thought it means all data.
is <ALL Values> a system field?
Thanks you.
Hi Avinash
That was my initial script...
I doubt that you have so many users in the QVD that it will make a significant performance difference.
<All VALUES> is just a syntax I commonly use to indicate that I expect to get all values. To me this signals a clear intention with the reduction value, compared to leaving the field blank. If you accidentally load a blank value, the blank field would not represent all, but the actual blank value.
This is an effect of how the reduction value is applied. See my post on Section Access: Strict Exclusion for an example of why an non-existing value returns all values.
OK try something like this:
Section Access;
LOAD * INLINE [
ACCESS, NTNAME, COST_CENTRE, CODE_2
USER,DOMAINNAME\Johna , *, A12
USER, domainname\peterz ,*,*
USER, domainname\paulo ,*,*
USER, domainname\kevinw , 2101,*
];
section application;
Load * inline
[
NTNAME,COST_CENTRE, CODE_2
DOMAINNAME\Johna , *, A12
domainname\peterz ,*,*
domainname\paulo ,*,*
domainname\kevinw , 2101,*
];
refer this document
check is data splitted properly across your section access condition. i mean there should not be any left out data which will not match any of scetion access data. and also check is there any null values in the section access given data.in your case that must be cost center and code_2
Thank you this seems to work really well.
I am still testing it . but it seems to be working correctly