Section Access

[Hariprasad]

Hi ALL,

For section access when i try to run all scenario's with different user's getting wrong vales, if i comment 1 by 1 it will work.

as per requirement all scenario's should work with different user's with right vales. 

INLINE

[
ACCESS, USERID, WMC, VEH_MODEL_SERIES_CD

 ADMIN, EMEA\hel, 3MX , *

USER, EMEA\fwin, 3MX , 177
ADMIN, EMEA\nkgu,* , 177
ADMIN, EMEA\boe, * , 177|207
ADMIN, EMEA\aha,* , *

](txt, comment is '//');

section Application;

[micheledenardi]

Have you tried to comment out the Section Access; statement and check if selecting user by user the result is correct? just to be sure the section access table is correctly lined to the datamodel...

Why there is (txt, comment is '//') at the end of the inline statement?

Try to use this approach: Basics for complex authorization  

[Mark_Little]

Hi 

Been a while since i have looked at section access, but i remember that there can be issue with using the * as i wild card. If i remember correctly need to link the * all the available dimensional values.  

[NadiaB]

Hi @Hariprasad 

It was not clear to me how the test was done, are you saying that if you remove all users, the one you leave in the table works?

Our documentation for Section Access is in the following URL 

https://help.qlik.com/en-US/sense/November2022/Subsystems/Hub/Content/Sense_Hub/Scripting/Security/m...

There are some samples that you could test initially to do some testing. 

Some things In general would be that all values have to be in CAPITALS, and the * works only for previous listed values, sometimes it is assumed that it will include all values in the data model "The wildcard character * in the data reduction column refers only to all values in the security table. If there are values in Section Application that are not available in the reduction column of the security table, they will be reduced."

Hope it helps.