Security help

[hopkinsc]

ARRGGGHHH! i am losing the will to live!

Can anyone help me to get SECTION ACCESS working please?

I am trying to reduce data by 2 fields (Sales Pool and Salesman).

I want to use NTNAME and have a backup ADMIN hardcoded into the script, i want to load in the data from an excel sheet.

I have attached an excel file with the data needed.and an example of what i want to do is..

ADMIN can see everyone and all regions.

USER1 can see [Sales Pool] DIR and  SalesmanAlec Nicolson and Alec Ross

USER2 can see  [Sales Pool]DIR and  SalesmanAndrew Mason, Anthony Boole, Archie Leitch

USER3 can see everyone in [Sales Pool] LG

USER4 can see  [Sales Pool]CON ans SalesmanLes Daubney

I have looked at loads of examples on here but can't seem to get it working.

Can anyone help please?

attached are the samples, i dont know if the way i am trying to do it is too complicated or not.

Any help would be appreciated.

The hardcoded userid is ADMIN and password is ADMIN

Thanks

[#2]

Hi,

try to replace your load script with this:

Security:

LOAD ACCESS,

     NTNAME,

     [SALES POOL]

FROM

[Userlist.xls]

(biff, embedded labels, table is [Domain Names$]);

left join

LOAD [SALES POOL],

     SALESMAN

FROM

[Userlist.xls]

(biff, embedded labels, table is [Salesman$]);

section access;

STAR is *;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD, NTNAME

    ADMIN, ADMIN, ADMIN, *

];

Concatenate

Load * Resident Security;

Section Application;

Drop table Security;

Data:

LOAD Region,

     Company,

     Salesman,

     Sales

FROM

[TESTDATA.xls]

(biff, embedded labels, table is [Sheet1$]);

Regards

MC

[hopkinsc]

Hi, thanks for the reply.

That isnt working with NTNAME and no data restriction is being done by salesman.

[hopkinsc]

Any more help on this from anyone would be appreciated

[rwunderlich]

You can't reduce on two fields. You must make a new field that represents the combinations of fields and reduce on that new field. You can find some examples of this here on the forum or in this post

http://community.qlik.com/blogs/qlikviewdesignblog/2012/10/02/complex-authorization

-Rob