section access problem

[#1]

Dear all,

I'm trying to use Section Access without success. I've this scenario:

SECTION ACCESS;

LOAD * INLINE [

ACCESS, USERID, PASSWORD, Group

ADMIN, ADMIN, ADMIN,

USER, USER1, U1, 07

USER, USER2, U2, 08

USER, USER3, U3, 06

USER, USER4, U4, 20

USER, USER4, U4, 21

USER, USER5, U5, *

];

User1 can see the group 07 only, ... user4 can see information about  20 and 21 groups...

The problem is that the data filtering  doesn't work and I don't know why. When I open the document, user and password are required, but all the users

see all the information

Some questions:

"Group" is a field name: is it important if I write it in capitals or small ?

If I logged as user1, what happens if I press the loading botton ?

Thanks in advance for your help

[hopkinsc]

Hi Stefan.

I think you put a '*' into the Group field for that person, that should allow him/her to see all groups.

I'm not very good on section access but im 90% sure thats how it works.

I also think that making that person an ADMIN will stop all restrictions.

Hope it works!

thanks

Chris.

[IAMDV]

Answers :

1. From Help Documentation :

A wildcard, i. e. *, is interpreted as all (listed) values of this field, i.e. a value listed elsewhere in this table. If used in one of the system fields (USERID, PASSWORD, NTNAME or SERIAL) in a table loaded in the access section of the script, it is interpreted as all (also not listed) possible values of this field.

Please be very careful using the '*' (Wildcard) because it doesn't mean all the values in the Actual Field. It means distinct values you have specified in Section Access Table. Unless you have specified all the distinct values within Section Access.

In your Section Access example, you have specified Group values as {06,07,08,20,21} but if your actual Group field contains {06,07,08,20,21,30,31} then you won't see {30,31} rows even if the User has '*' in Section Access. It will ONLY take all the values from Section Access but not all the values from actual field.

I hope that makes sense.

2. I'm assuming that you are not using "Strict Exclusion". If this is the case then you need to leave the "Group" field blank to give Full User Access. The process is different if you are using "Strict Exclusion".

Cheers,

DV

www.QlikShare.com

[#4]

It's very very clear.

concerning the second question, I'm using "Strict Exclusion".

I n this case, do I have to build a table with all the combinations ? It seems a bit hard to manage

Gr.

Stefano 

[IAMDV]

I'm glad to know that it makes sense.

Yes, you are right...makes me feel silly to psuedo code one user with all other possible options to provide full access, which is painful. But that's how it works unless I'm missing something important here. Also "Strict Exclusion" works fine with one field but if you have hierarchy table for Section Access implementation then it's going to be laborious job. I generally avoid using "Strict Exclusion" in Hierarchy - Section Access implementation. Rather I'll deal with it seperately with extra care but that's different topic for discussion.

You are not a beginner for sure...know your stuff!

Cheers,

DV

www.QlikShare.com

[IAMDV]

I'll create video tutorials and post them on my blog. I'll update this thread whenever I do that...

Cheers,

DV

www.QlikShare.com