topic Re: Help with Section Access in QlikView

Help with Section Access

triciagdaly — Wed, 15 Apr 2015 17:26:17 GMT

I am trying to load access for users with price list (CPL) access, and unable to load from the qvd. It will accept loading using INLINE. In other words, when logging in as 'nparker', the CPL displayed is 'KRL'. I need to use the qvd, not INLINE. Please see attached qvw that builds the .qvd 'CreatePricingAccess.qvw', and the .qvw with Section Access.

In this application - 'Customer Pricing - TGD.qvw', user 'tdaly' should have access to all CPL's when logging in and supplying password of 'Password1'. It will only accept nparker (from the INLINE).

Data from qvd is also attached in Pricing_Access table.docx

Re: Help with Section Access

Wed, 15 Apr 2015 17:37:06 GMT

Can you unhide your hidden script so that I can take a look at your section access code?

Thanks.

Re: Help with Section Access

triciagdaly — Wed, 15 Apr 2015 17:46:07 GMT

This is the code in the hidden script:

SECTION ACCESS;
LOAD ACCESS,
NTNAME as USERID,
'Password1' as PASSWORD,
CPL
FROM
[..\QVD\PricingAccess.qvd]
(qvd);

Concatenate
LOAD * INLINE [
ACCESS,USERID,PASSWORD,CPL
ADMIN,nparker,Password1,KRL
];

Section Application;

Re: Help with Section Access

Wed, 15 Apr 2015 18:04:33 GMT

First thing I'd do is give the section access table a name. Then concatenate against that table name. The other thing I'd make sure of is that you are indeed creating a list of users from your QVD that includes valid values from the reduction field that exist in the data.

Next thing I don't completely understand is why not create the appropriate field names for section access and include the password field in the qvd creation instead of etl when you pull in the QVD? Seems like double work and it's not clear to me. You are going from using NTNAME to using USERID. Is there a reason for that?

The script above looks ok to me, but I have a feeling there is something that isn't correct with the qvd creation.

Re: Help with Section Access

quwok — Wed, 15 Apr 2015 18:06:03 GMT

Do you have to concatenate the table?

When we played around with section access, it seems that QlikView does not like the table to be created in two parts and merged together.

Re: Help with Section Access

triciagdaly — Wed, 15 Apr 2015 18:07:51 GMT

No, we only concatenated to be able to see which section was working.

Re: Help with Section Access

Anonymous — Wed, 15 Apr 2015 18:09:08 GMT

Try this small change:

upper(ACCESS) as ACCESS,

upper(NTNAME) as USERID,
'PASSWORD1' as PASSWORD,

Re: Help with Section Access

triciagdaly — Wed, 15 Apr 2015 18:12:47 GMT

Jeffrey,

Regarding the field names, we will just use NTNAME when this goes to production, and comment out the USERID and PASSWORD assignment .. While in test, we want to be prompted for userid and password.

Regarding the list of users generated from the qvd, the list appears correct. Also, from the table I attached, user 'tdaly' should be able to view all CPL's. Will not open application with this or any other user that's not included in the INLINE.

Puzzled....

Re: Help with Section Access

quwok — Wed, 15 Apr 2015 18:16:31 GMT

In that case, try dropping the concatenate and add "where 1=1" to your QVD load. Your script should look like

SECTION ACCESS;
LOAD ACCESS,
NTNAME as USERID,
'Password1' as PASSWORD,
CPL
FROM
[..\QVD\PricingAccess.qvd]
(qvd)

WHERE 1 = 1;

Section Application;

Re: Help with Section Access

triciagdaly — Wed, 15 Apr 2015 18:18:36 GMT

Michael,

This worked! Thanks so much!!!

Tricia

Re: Help with Section Access

Anonymous — Wed, 15 Apr 2015 18:20:51 GMT

It always does

The data in section access must be in all capital, unless it is load inline. Even if I know "for sure" that the values are all caps, I always use upper() in section access.

Re: Help with Section Access

triciagdaly — Wed, 15 Apr 2015 18:24:01 GMT

Michael,

Is this a recent requirement? We have older applications that are not using uppercase... for example in the password it's 'Password1' that was used for testing.

Re: Help with Section Access

Anonymous — Wed, 15 Apr 2015 18:31:49 GMT

It's been this way since the beginning of time... I'm sure it is documented in "help". Mixed case works in inline load, but I don't have high expectation with any other load.