Section Access logic works the same way on QlikView Desktop and QlikView Server side. This means we need to provide access to the user executing the reload task and prevent the data from being reduced.
Otherwise, the reload will fail with Access Denied or the application will not include as much data as expected.
In this example, the QlikView Server service account and the application developer are expected to get all values in field F1. The application end-user on the other hand has limited access to the field F1.
The application and Section Access works as expected in the QlikView desktop client. The developer gets access to all values in F1 and the user gets limited access in the document. The basic 'deployment' flow in desktop will be as below:
Application is reloaded by Developer
Application is saved to file by Developer
Application is opened by User
Application get reduced based on User's reduction value A
The application shows limited values in F1 to User as expected
On the server-side, the workflow will be a bit different, potentially leading to unexpected results for the User.
Application is opened by the Service user
Application is reloaded by the Service user
Data in the QVW file is reduced based on the Service user reduction value
Application is saved to QVW file by the Service user