When using Section Access and Dynamic Data Reduction, Strict Exclusion option in Document Properties\Opening tab should be set

When using Section Access with Dynamic Data reduction fields in the Section Access table in the QlikView Product, it is very important to note the Strict Exclusion setting should also be enabled to ensure the expected behavior is achieved.

R&D will be hesitant to review any use case where Dynamic Data reduction fields are being used and Strict Exclusion option is not set.  The separate setting was for legacy related purposes back when the feature was introduced in version 7.52, the setting should be considered mandatory to ensure expected behavior of reduction of values is properly obtained.

 

Please review the following posts to ensure the best outcome when attempting to use Section Access with Dynamic Data Reduction in QlikView:

Community post:
https://community.qlik.com/docs/DOC-8562

Design Blog posts:
http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access
http://community.qlik.com/blogs/qlikviewdesignblog/2014/06/02/data-reduction-using-multiple-fields
http://community.qlik.com/blogs/qlikviewdesignblog/2014/06/09/methods-for-data-reduction

Latest Help information:
If this check box is marked in combination with Initial Data Reduction Based on Section Access, strict exclusion will be used when reducing the data. This means that access to the document will be denied whenever the field values in the section access reduction fields lack matches in their corresponding section application field. This, however, does not apply for users with Admin status, who instead will see the unreduced data set if there are no matches.