I was recently helping a colleague debug a problem where Section Access in a Qlik app was not working correctly. It was not allowing access to listed users. Amongst other script he had an Inline load that looked something like this:
I pointed to the values of the USERID field and said “There’s your problem. The USERID values have to be in upper case. All values in a section access table have to be in upper case. It’s in the Doc”.
“No…” he replied, and proceeded to show me other Apps that used lower case USERID values and did work correctly. I looked at a few of my own apps and found some with lower case values, working correctly.
Why did the problem App fail while others worked? What was different? The difference is that in the problem App, the Load Inline occurred in Section Application and was subsequently Loaded Resident in Section Access. So what? I would have never found the cause but for a Qlik Community post from 2012.
When Load Inline is used within the script Section Access “section”, all data is automatically transformed to upper case.
Whoa! Double whoa!
Load sources other than Inline are not transformed in Section Access. And the magic transformation doesn’t happen in Section Application. I’ve never seen this behavior in the Qlik Doc.
Did everyone know this but me? Is it documented somewhere?
-Rob
Never heard about that. Section Access always has that little remaining mythos (Greek for mystery) around it 😉
I had never seen that ..
I always say that Section Access is always right and if it doesn’t work it’s because we’re doing something wrong but i must admit it is the most complicated and tricky thing in Qlik… Too bad they have not made something easier to user as it’s really powerful
I never knew that inline within section access was automatically upper case. I had similar experience to yours, couldn’t explain it-now i can!
Thanks Rob!