I have a qvw file with section access. The purpose is that, I want to restrict data visibility based on the attached file(just an example). Admin can see all country data, and users can only see their country data.
When I reload the file on desktop manually which is placed inside Qlikview\SourceDocument folder it runs fine, and then I use to place the qvw inside Qlikview\documents folder so that users can access via Access point. By following this process it works.
But, I want to be a scheduled run on the server, and I have created a task in QVMC which run fine. The document is also distributed to Qlikview\documents folder.
Now when i try to access the qvw using access point I get error msg: Failed to open the document, you might not have permission.
I have also added QV_ADMIN user in the list through which all our Qlikview services runs on the server. I came to know about this somehow from the community and google.
What else I'm missing here or I need to do some other way ? Let me know if any more detail is required.
When creating your Section Access table, always use the UPPER() function to convert USERID, PASSWORD, NTNAME and whatever to upper case. Especially when loading from an external source. Solves a lot of Section Access mysteries. Maybe yours will be solved too.
Do I understand it correctly that before data reduction, you try to associate User_Visibility and User by way of two fields (NTNAME and COUNTRY_CD)? QV does not create synthetic keys for tables in Section Access...
A solution to this can be to create a Users key from both NTNAME and COUNTRY_CD. The annoying thing is that you loose '*' functionality. You'll have to do the expansion yourself. Or just drop the NTNAME link.
It's no use to create a User_Visibility table with exactly the same fields as Users. User_Visibility will have one unique field that links to section access, and other fields that link to the rest of the data. It's contents is just a list of all possible countries that are available in your data, not in the security file. To see this, imagine that you have a country called GRMBL that has data available but no ordinary user should be able to see it. You'll expect QV_ADMIN to have access to GRMBL data, but QV_ADMIN only specifies *, and country GRMBL won't occur in your security excel. The * of QV_ADMIN will expand to all values from column COUNTRY_CD in table User_Visibility that doesn't include GRMBL...
