I think our issues revolve around interpretation of this phrase in the manual
USERID Contains a string corresponding to a Qlik Sense user name. Qlik Sense will get the log-on information from the Proxy and compare it to the value in this field.
Basically am I
QMC screenshot below
I Think NTNAME is no longer valid....?
- Qlik Sense no longer uses windows accounts internally in the product. This is the main reason for changing to USERID and if we are not using windows accounts SID make no sense. In Qlik Sense all accounts work the same way independent if they are accounts coming through tickets, SAML or header. Fredrik
A couple things to try:
- Renaming the user so that it has no spaces (Use "_")
- Be sure that your data model shows a link between your section application table (as I mentioned above) and an existing table
- This join, based on what you have provided, should occur on the Value field
- Be absolutely sure that the Values (1000, 420, 100) actually exist in your data set
- Flip the order of your Load inlines so section access comes first, and then section application.
Here is a screenshot of what mine looks like (which works) for comparison.
I am heads down preparing for Qonnections, and unfortunately I have not explored section access to its fullest yet, so I cannot answer this off the top of my head. ( I plan on making a video on it this year though.) I will add jog and jpe to this discussion to see if they can provide any advice. They are busy as well, but I know they are always willing to help when they can.
Please mark the appropriate replies as CORRECT / HELPFUL so our team and other members know that your question(s) has been answered to your satisfaction.
If I can add to @Tim Kendrick avoid spaces in userids if you can help it.
Prior to Qlik Sense 2.2, there was an issue with Section access and non-url encoded values. So you may have to enter an urlencode character for the space %20.
In addition, no need for the omit column if you aren't using it. you do need to mark section application, whether your load comes before or after section access statement.
The question I have is what does your data look like after you load this script?
Perhaps this will help
Here are my findings based on the testing I've done so far on QlikSense Section Access
- The Section Access table must have EVERYTHING in Uppercase
- The fields that you are wanting to use in your data model as restrictions must have their Field Names and Values in Uppercase
- USERID can have spaces but my user ID for example AGGUK\Helen Chapman must be entered in the Section Access table as AGGUK\HELEN+CHAPMAN, all in Uppercase replacing the space with the + sign
To avoid duplicating effort from that already completed for QlikView I have a Qlikview QVW file containing my data model with Sales data linked to our Business Unit (Cost Centre) structure that I have Binary Loaded into Qlik Sense.
I want to give John Smith access to only our Aggregates Division (UKDivisionCat19 = AGG - Aggregates) sales data but Joe Bloggs should only have access to the Aggregates North part of the Aggregates Sales Data (UKDivisionCat19 = AGG - Aggregates and OpDivisionCat05 = AGN - Aggregates North) whilst I, working in IT, should have access to all the data.
My section access table should look like this:
load * inline [
ADMIN,AGGUK\HELEN+CHAPMAN,, //leaving out the values in the restriction fields gives full access
then to apply the section access I need to reload the mixed case fields I want to use from my binary loaded data model and create tables that give me the fields I need with their Field Names and Values both in Uppercase
left(UkDivisionCat19,3) as UKDIVISIONCAT19,
UkDivisionCat19 //link back to existing Field in the Binary loaded table
left(OpDivisionCat05,3) as OPDIVISIONCAT05,
OpDivisionCat05 //link back to existing Field in the Binary loaded table