Ideas why filter accesspoint view based on section access works for only some documents?

[stevelord]

Hi, I'm just looking for some sort of brainstorm from anyone else who experienced this issue, and what the solution was in their case.

All of the documents have the box checked to filter accesspoint view based on section access.

All of the documents have the same piece of section access script.

Some documents are not visible to people outside the section access list. (desired result)

Some documents remain visible to people outside the list. (why?)

Any random or educated guess on why this would be?  I know our server configurations may vary, but I'll take whatever insights or ideas anyone here has on this and see if they apply or can be adapted to my specific situation.

I'll give helpful answer to pretty much any of the first replies, and correct answer to whatever causes me to at least land on a path that leads to a solution.

[maxgro]

is stric exclusion checked or only initial data reduction...?

[stevelord · Accepted solution]

Actually, I solved it.  For some reason the word section was being read as a word instead of the start of the command in some scripts but not others.  All of the visible characters in the area looked the same, so thinking it was something invisible I squashed to resolve it.

Weirdly, when I did re-enter it either by the section access wizard or selecting the command from the dropdown when I typed it, it looked like a command then (word 'section' was in bold), but when I deleted the bad script above it it went back to treating it like a word (word 'section' went to regular text).

To resolve, I took the entire first bit of script in one of the working section access qlikviews from the bottom of the section access inline table (section application;) to the top of the SET variables that qlikview provides, and copy/pasted THAT into the start of the qlikviews that were not correctly reading the section access inline table.  And that worked.  Something invisible to me in that area of the script was causing the command to be read as a word instead of a command in some of the qlikviews but not others, even though I'm pretty sure I haven't done anything there. (It was just the default SET lines, a blank row, and then the section access inline table in them.)

One weird clue that got me digging into the characters of the script was the fact I could see ntname and access as fields in the sa qlikviews not working and not as fields in the sa qlikviews that were working- I thought maybe I had a colon instead of a semi-colon or something, but that wasn't it and everything looked sharp when I zoomed in on it etcetera.  Ultimately I just stepped on the ghost anomaly with a copy/paste of script that was working okay.

[stevelord]

Thanks Massimo, those boxes are actually unchecked at the moment across all of the qlikviews.  I was focused on just making qlikviews disappear from the accesspoint view of people who can't access them anyway.  So I focused on the stuff on the server tab there.  Since that group of people won't be seeing or opening the qlikviews, the stuff on the opening tab might not be necessary yet.

(Only funny thing left for me to figure out is why there are qlikviews I can see on accesspoint, but not in the qlikview server documents folder, and I suspect that one's just me needing someone to set me one step higher as a superadmin instead of a sortofadmin on the qlikview server.   Or I'll just give them a list and some script for them to fix those themselves...)