OK can you please post your section application code...
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.
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.
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?
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:
LOAD * INLINE [
ACCESS, NTNAME, COST_CENTRE, CODE_2
USER,DOMAINNAME\Johna , *, A12
USER, domainname\peterz ,*,*
USER, domainname\paulo ,*,*
USER, domainname\kevinw , 2101,*
Load * inline
DOMAINNAME\Johna , *, A12
domainname\kevinw , 2101,*
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