Section Access Befuddlement

[JustinDallas]

Hello Folks,

I'm working with adding Seciton Access to  our system.  As of now, I see the OMIT clause is working as intended, but when it comes to Reduction, it's failing.  My script looks like this:

But when I run the app in question as the user, I see this.  They still have access to where [Dest State] <> 'GA'.

What's going on here?

Any help is greatly appreciated.

[rittermd]

You might need the Domain\ in front of the user name.  Or whatever User Directory you loaded them from.  Check the QMC.

[JustinDallas]

I've got the Domain in the redacted text.  I see the OMIT value working as intended, but I don't see the field restriction working as intended.

[JustinDallas · Accepted solution]

The documentation says that the field in the "Section Access" must be capitalized, but I don't think it said that the field name on the tables of interest had to be captialized too.

Once I capitalized my Table field [Dest State] => [DEST STATE], everything worked as intended.

[Anonymous]

This is a rear case where you have to mark your own reply as correct.  It is correct, and it's helpful to make the thread closed.

[rittermd]

Glad it worked for you.  The problem is that the field with caps in your inline table does not match the actual field name.  As you probably know, Qlik is case sensitive.  The field names have to match exactly.