Section Access - Reduction field showing all values

[#1]

Hi all

We use the reduction field [RANGE] to not only reduce the data shown in a report, but also to show/hide a number of the sheets.  Here is the section access code.

Section Access;

Security:
LOAD [ACCESS],
NTNAME,
RANGE
FROM
..\..\Security\Spreadsheet.xlsx
(ooxml, embedded labels, table is ACCESS);

SECTION APPLICATION;

Reduction:

LOAD RANGE,
Transaction
FROM
[..\..\Security\FinanceAccessControl.xlsx]
(ooxml, embedded labels, table is RANGE);

The values for [RANGE] are either 'ALL', 'AP', 'AR' and a [NTNAME] is only assigned one of these values. *NOTE for the service accounts the [RANGE] value is blank.

The formula for show/hide of the sheets is based on the following (with variations according to who should see the sheet)

=Only({1}RANGE)='ALL' OR Only({1}RANGE)='AR'

Intermittently, in both the desktop application and in AccessPoint, all the show/hide sheets are hidden, and a debug tab shows that the [RANGE] field contains all three of the available values, which makes the Only() functions in the show/hide formula return NULL.

Reopening the .qvw in the desktop application solves the problem, and restarting the QVS service solves the problem in AccessPoint.

Has anyone seen this before?  And more importantly, do you know what causes it and how it can be resolved?

[Peter_Cammaert]

Do you have option "Strict Exclusion" enabled in Settings->Document Properties->Opening?

[#3]

[Peter_Cammaert]

There you have it. If a user enters a document with section access and strict exclusion disabled and data reduction reducing away all data (because of no linkage, wrong link values or simply no relevant data) then he or she will get access to everything. That's standard QlikView behavior.

Enable "Strict Exclusion" if you want the door closed for people that shouldn't get any access. They won't see a thing anyway...

Good luck,

Peter

[#5]

Hi Peter

Thanks for the info, however your solution only allows me to further secure the document should the data reduction not work properly, which happens intermittently.

As mentioned, reopening the QV app or restarting the QVS service seems to remedy the problem when it occurs.  But I am trying to establish why we are experiencing this intermittent problem.

Thanks

James