topic NTNAME in section access in QlikView

NTNAME in section access

Anonymous — Tue, 18 Mar 2014 04:13:43 GMT

Hi all, quick question, in section access if I'm just using NTNAME and again NTNAME as User, to reduce based in ntname via a bridge table, should the NTNAME be in upper case or just user? It's denying me access to document in access point but not in desktop, I'm using both reduce data on load and strict exclusion.

Current code:

SECTION ACCESS;

LOAD upper(ACCESS) as ACCESS,

upper(NTNAME) as NTNAME,

upper(NTNAME) as USER

FROM

[http://ent264.sharepoint.hp.com/teams/QlikViewSCO/Repository/360Dashboard/AccessList.xlsx]

(ooxml, embedded labels, table is 360);

Thanks for your help!

Re: NTNAME in section access

Anonymous — Tue, 18 Mar 2014 20:15:04 GMT

It the strict exclusion issue. I had it too, and everything works after unchecked.

Still, you don't want to have full data access to the users who don't have relevant data. I resolved it by adding dummy data for the restricted users. They can open the application, but have nothing to see there.

Re: NTNAME in section access

Gysbert_Wassenaar — Tue, 18 Mar 2014 20:16:14 GMT

Just a thing to keep in mind. All users will get USER access when opening the document through the Access Point. ADMIN access isn't available through the Access Point. And do the users also have read access file permissions on the .qvw file on the qlikview server?

Re: NTNAME in section access

Anonymous — Tue, 18 Mar 2014 20:19:04 GMT

There are more files in accesspoint, some users should not be able to view them all. What happens if I uncheck strict exclusion, but their NTNAME is not in section access table? Will they still have access?

Re: NTNAME in section access

Anonymous — Tue, 18 Mar 2014 20:30:39 GMT

Seeing an application in the Access Point and ability to open an application are two different things.

You can distribute applications to the selected users and groups, so only they can see them. But section access can still prevent apps from opening. If NTNAME is not in section access, user cannot open the application, regardless the "strict exclusion" checkbox.