Completely Confused by Section Access in Qliksense V2

[timsaddler]

Apologies but having read several threads, I'm no nearer to getting this to work.

Here are my scripts

load * inline [

BUSINESSUNIT, VALUE

4501399, 1000

4224399, 420

4228399, 150

];

section access;

load * inline [

ACCESS, USERID, BUSINESSUNIT, OMIT

USER, AGGUK\tim saddler,4501399,

USER, AGGUK\helen chapman, 4224399,

];

screenshot of QMC user ids

Any pointers would be most appreciated

Thanks in advance

[simondachstr]

You don't have NTNAME in Qlik Sense, only UserId & Groups, identical to the QMC.

Sections in the script ‒ Qlik Sense

[simondachstr]

Not field names or field  values!

[timsaddler]

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

Saddler, Tim

tim saddler

AGGUK\tim saddler

[AGGUK\tim saddler]

QMC screenshot below

[simondachstr]

Try writing your userid value in upper case, e.g. [AGGUK\TIM SADDLER]

Even preferably, when loading the data, use the Upper() function on UserID.

[er_abhichandra]

Hi Martin, I think you misinterpreted my statement, I meant all field names and field values in the Section access table needs to be in uppercase.

Thanks,

Abhinava

[simondachstr]

Hi Abhinava,

This is indeed what the Qlik Sense manual is stating so you definitely got a valid point. However,for dynamic data reduction party, the fieldnames & field values have to be identical to the one in the data model as they are case-sensitive.

[TKendrick20]

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.

[#9]

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?

[er_abhichandra]

That are absolutely correct Martin. Hence you need to duplicate all the fields in the data model in uppercase which involved in the section access .

[simondachstr]

I have tested this and it works even if the values are lower case in the section access table.