topic Re: Will Section Access rebuild on server if Perform Reload is unchecked? in QlikView

Will Section Access rebuild on server if Perform Reload is unchecked?

Tue, 22 Apr 2014 18:00:36 GMT

I have a document that has Section Access for reducing the data for users coming in by SSO. I have moved the document up to the server, created a task to distribute the file, and checked the Section access check box on the Data Protection section on the Reload tab. I did not check Enable under Perform Reload. The task will run even if I put junk in the User name text box for the username. Needless to say, the section access does not apply when the document is loaded into the portal that is calling this doc.

Is the Section access ignored in the task when there is no reload enabled? The section access part of the document was copied from a test doc that is essentially the same with less data, so I am fairly confident that it should work.

Re: Will Section Access rebuild on server if Perform Reload is unchecked?

Chris_Rice — Tue, 22 Apr 2014 21:28:51 GMT

That section is specifically for defining another username/password to be used when reloading the document:

Data Protection

Section Access

By default, the reload will be performed as the user under which the QlikView Distribution Service (QDS) is running. The Section Access setting allows the use of another user when performing the reload. To by-pass the default setting, tick this check box and enter the desired user and password in theUser Name and Password text boxes. To use the default setting, untick this check box.

If you're just doing a distribute the Data Protection section under the Reload tab is ignored, so you'll have to add the Distribution Service Account to your Section Access list.

Re: Will Section Access rebuild on server if Perform Reload is unchecked?

Tue, 22 Apr 2014 21:42:39 GMT

The Section Access part of my load script has the Distribution Service Account in it, and the file that I moved up to the server has that section access in it. I'm attempting to determine if the section access in the document is active in the file I distributed. It does not appear to be, as every user we've tried so far has access to all the data.

So my reading of the text above, which to me is not completely clear, is that Section Access checkbox, if clicked, will provide a different user credential to load section access, but if the Reload checkbox is not checked, then NOTHING will happen with section access? Shouldn't the section access in the file still be valid? Does publisher publish the document with the existing section access in the document, or does it not deal with it if reload is not checked?

Re: Will Section Access rebuild on server if Perform Reload is unchecked?

Tue, 22 Apr 2014 21:45:25 GMT

Sorry, all. The last reply was by me. Somehow when I click on the post in MY email, I end up logged in as him.

Re: Will Section Access rebuild on server if Perform Reload is unchecked?

Chris_Rice — Tue, 22 Apr 2014 21:50:19 GMT

You're right, it's not clear. If the Reload checkbox is not checked, that tab is basically ignored. If your service account is part of the Section Access script, the Section Access in the QVW should be retained when distributed by the Distribution Service. If it's not being retained, most likely there's something wrong with the SA script. Usually this is a reduction field for the Service Account. If you do have a reduction field, just put "no reduction" for the Service Account and it should work. I hope that makes more sense. Please let me know if I've missed something.

Re: Will Section Access rebuild on server if Perform Reload is unchecked?

Tue, 22 Apr 2014 22:01:36 GMT

Thanks for the help! That clears some things up for me.

My document's section access looks like this:

SECTION Access;

Admin:

Load * Inline [

ACCESS, NTNAME, PR_ID

ADMIN, XXXXXXX\BGIBB,

ADMIN, SVC_QLIKVIEW,

ADMIN, BGIBB,

ADMIN, ADMIN,

];

Concatenate

LOAD 'USER' as ACCESS, Advisor_key AS NTNAME, Advisor_key as PR_ID Resident Advisors;

SECTION Application;

AdvisorAccess:

LOAD Advisor_key AS PR_ID, Advisor_key Resident Advisors;

What it is supposed to achieve is letting the advisor see only their own stuff. The get a ticket using PR_ID, that gets passed to the document and should therefore be the NTNAME. My Admin table should have all the advisors set up as USER with the NTNAME equal to the PR_ID. It worked as written once in a test document with much of the same data, but when I added the rest of the data, everyone sees everything. I'm at a loss, and up against a deadline. Sigh