Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
vijetas42
Specialist
Specialist

Section Access

Hi all,

We have issue with files on which we applied section access.on accesspoint it's showing error like,

failed to open document.previously they works fine.please find attached screenshot.and give your solutions.

We also check section table for all users we have entry in it.

section.PNGThanks!

3 Replies
krishna_2644
Specialist III
Specialist III

Hi Vijetha,

This message shows that the user is not authorized to see the document even though that user exists in the section access.

so check the User whether the user is authorized to see the doc or not.

let me know if you have any questions.

Thanks

krishna

Clever_Anjos
Employee
Employee

It seems that the user you are using to open the QVW is not in Section Access section.

Please use one user that is in SA or use a backup, there´s no workaround

Anonymous
Not applicable

Hi Vijetha,

     You say "previously they works fine" was it before you applied section access

     or it was working fine with the QlikView desktop client ?


     May be this will help you, please take a look at this https://community.qlik.com/docs/DOC-8633


Here is an extract:


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.

2015-05-24 11_36_18-Edit Script [C__Users_tko_Documents_Community Content & Material_Content - Secti.png

On server side the work-flow will be a bit different, potentially leading to unexpected results for the User.


  1. Application is opened by the Service user
  2. Application is reloaded by the Service user
  3. Data in the QVW file is reduced based the Service user reduction value
  4. Application is saved to QVW file by the Service user
  5. QVW is distributed


The distributed QVW file now has reduction values that matches the Service user. In this case it means that REDUCTION field only has ALL as possible value. The User's reduction value A does not exist, and this can lead to two different outcomes when the User opens the application through a web client.

If Section Access: Strict Exclusion is enabled, the User gets access denied since there is no possible data for the User.

Basically the Service User needs to have access to all reduction values, so that it covers all the users needs. By using wildcard star the reduction is equal to all listed values in the section access table.

Solution1.png

Regards,

Luc