Databases Reference
In-Depth Information
We have now set up the document to, upon opening, exclude all of the data that the
user does not have access to. Let's have a closer look at the options that we set in the
Document Properties:
•
Initial Data Reduction Based on Section Access
: This option enables initial
data reduction for the document.
•
Strict Exclusion
: When set, QlikView denies access to users whose data
reductions fields cannot be matched to values in the data model. This does
not apply to
ADMIN
users, who will instead get access to the entire data
model. It is recommended to always enable this option to prevent unwanted
access to data within the document.
•
Prohibit Binary Load
: When set, it is not possible to load the document
into another QlikView document using a binary load. It is recommended
to always enable this setting unless you are using a multitiered data
architecture that uses binary loads, for example, when using QlikMarts.
When a document containing section access is loaded into another document
using binary load, the new document will inherit the section access of the original
application. Take a minute to try logging in as the
DUDF
and
IF
users and see how
the data is reduced to show only the authorized flight types. After that, reopen the
document and log in as the
ADMIN
user, we'll need the privileges to make our next
changes.
Omitting fields
While looking at the fields in the
Access Restriction Table Wizard
, you may have
noticed that there is one field that is a little different from the others: the
OMIT
field.
While all of the other fields are used to identify a user, the
OMIT
field is used to
remove fields from the data model for the specified user.
In the next exercise, we will create a new user,
NOCARRIER
, and will remove the
Carrier Name
field for this user. Let's follow these steps:
1.
Open the script editor by pressing
Ctrl
+
E
and select the
Hidden Script
tab.
2.
Update the section access
INLINE
table by adding the
OMIT
field.
