topic Re: Section access using bridge table in QlikView

Section access using bridge table

Anonymous — Tue, 22 Sep 2015 12:21:52 GMT

I have attached qvw and qvd

Its working on desktop not on access point.I followed your post complex authorization

Thanks in advance

Re: Section access using bridge table

stigchel — Tue, 22 Sep 2015 12:53:40 GMT

In this sample you renamed the fields in the first qvd load and stored it again, so your bridge table does not load. Use the new fieldnames e.g.

Load [Reporting/Issuing Office] &'|'& [Local Branch Code] as AuthID, [Reporting/Issuing Office] &'|'& [Local Branch Code] as %AuthID

Re: Section access using bridge table

Anonymous — Tue, 22 Sep 2015 13:00:19 GMT

I am using this qvw for section access

Re: Section access using bridge table

stigchel — Tue, 22 Sep 2015 13:10:06 GMT

?? Yes, what is your point?

In the qvw you attached here, the load for the bridge table is failing as the fieldnames

([Rep-OffOO] &'|'& [Loc-Br-AnalOO])

do not exist because in the load before that you e.g use

[Rep-OffOO] as [Reporting/Issuing Office],

Which you then store into that qvd again

//Bridge Table used for Section Access

Bridge:

Load [Rep-OffOO] &'|'& [Loc-Br-AnalOO] as AuthID, [Rep-OffOO] &'|'& [Loc-Br-AnalOO] as %AuthID From $(HF_OGIS_QVD)(qvd);

Re: Section access using bridge table

Anonymous — Tue, 22 Sep 2015 14:01:57 GMT

Hi Piet,

I have corrected the qvd and qvw and uploaded.

same qvw is working on desktop but not working on access point

Re: Section access using bridge table

stigchel — Tue, 22 Sep 2015 14:16:14 GMT

Ah ok, what I notice is that the %AuthID field is not completely in capitals. For section access all fieldnames and field values must be in capitals. So try to change the fieldname to %AUTHID

From the help:

All the fields listed in Load or Select statements in the section access must be written in UPPER CASE. Any field name containing lower case letters in the database should be converted to upper case using the upper function, see upper(textexpression), before being read by the Load or Select statement. However the user ID and the password entered by the end-user opening the QlikView documents are case insensitive.

Re: Section access using bridge table

Anonymous — Tue, 22 Sep 2015 14:29:49 GMT

Thanks for reply

I have tested that also its working on desktop but not working on access point(failed to open the document).

Re: Section access using bridge table

stigchel — Tue, 22 Sep 2015 14:51:10 GMT

The failed to open document message actually suggests that the section access is working but that the user trying to open the document is either not (correctly) in the section access user list and/or there is no data for the user with the restrictions the user has.

I see that you have the domain included in the NTNAME field, can you try without, so instead of

R1-CORE\CBALAKRI

-->

CBALAKRI

Re: Section access using bridge table

Anonymous — Wed, 23 Sep 2015 07:48:10 GMT

Hi Piet,

its working on desktop for the same(R1-CORE\CBALAKRI) but not working on access point.

Re: Section access using bridge table

nancypoliti — Fri, 19 Jan 2018 21:07:32 GMT

This is the issue I am having. Was it ever solved?

Re: Section access using bridge table

Anonymous — Tue, 23 Jan 2018 00:30:47 GMT

I realise this thread is a few years old but as I found it while I was having the issue I thought I'd share.

With publisher, the document reduces by the access given to the service account user, before reducing for individual users.

That is, a service account user with access <ANY>|<ANY>, will reduce the entire document to this exact string, before attempting to reduce to ABC|XYZ. As ABC|XYZ doesn't exist any more (only <ANY>|<ANY> does), the access denied message is shown.

The simple solution is just to give the service account user blank access. I.e. an empty string, rather than <ANY>|<ANY>. This will mean all strings (i.e. no reduction) exist in the master app, so the reduction to ABC|XYZ will be allowed.