QlikView Publisher and Section Access Dynamic Data Reduction Best Practice
Article Number: 000017165 | Last Modified: 2018/06/12
Many customers utilize QlikView Publisher to perform their reloads and distributions. Some also utilize Section Access with Dynamic Data Reduction as well, and there are some key best practices that need to be kept in mind when developing the Section Access table in the load script in these cases to ensure everything works as expected.
A very important change in QlikView Publisher 8.00 and onwards compared to older versions is that QlikView Publisher respects the Section Access of any document wiht which it works. This means if you have a Section Access in your document script, the Publisher user or user account must have ADMIN rights according to the Section Access statement. If the Distribution Service is running under the local computer accounts Local System or Network Service, the computer account must be added to your Section Access. The account name of the computer is usually the name of the computer plus a $ sign, e. g. PublisherServer$. If a dynamic reduction is made, the reduction field must be left empty.
LOAD * INLINE [
ACCESS, NTNAME, REDUCTIONFIELD
USER, HIC, A
USER, TNI, B
It is important that the Section Access line containing the Publisher account does not reduce data in an unwanted way. Example: If you would use a wildcard “*” in the reduction field, this would limit
QlikView Publisher’s access to the data in the QlikView file to other values defined in the Section Access (A and B in this example; however, the values C to Z would not be included). Such a reduction can be avoided in two ways: either you need to make sure that all values of the reduction field are represented in the Section Access, or you leave the reduction field blank. In the latter case, no reduction will be made since the Publisher account is an ADMIN account. However, in this case, the Publisher account cannot be used to open the file on a Server since all accounts are USER accounts on a Server and the user will then be denied access since no values are allowed.
Read more about Section Access in the Security chapter of the QlikView Reference Manual.