This field is required.
Only these extensions are allowed(.jpg, .JPG, .jpeg, .JPEG, .gif, .GIF, .png, .PNG)
Tags cannot contain the characters ' /, \\, #, ?, or ; >,< '
Only these extensions are allowed(.zip,.ZIP,.pdf,.PDF,.qvf,.QVF,.qvw,.QVW)
If you’re new to Qlik Sense, start with this Discussion Board and get up-to-speed quickly.
I have created a custom property called GROUP in the qmc, which can either have the value G1 or G2. I have assigned this custom property to my users, some of them have G1, others G2.
My application has a dimension called DIM , which can have the values "A", "B" and "C".
I want to restrict all users who are in GROUP G1 (i.e. have the custom property value G1) to view all data that is connected to DIM values "B" or "C".
I also want to restrict all users who are in G2 to view every data that is connected to "A" or "C".
I have managed to make the section access work by defining the following inline table for each user manually.
LOAD * inline [
ACCESS, USERID, DIM, OMIT
USER, DOMAIN1\peter, "A",
USER, DOMAIN\max, "B",
But how can I define my behavior by means of Custom Properties?
I have tried this one as shown in the qliksense help page (*) but it gives me "Access denied" to every user:
ACCESS, USERID, GROUP, DIM, OMIT
USER, *, G1, "A",
USER, *, G2, "B",
you can't use Custom Properties with Section Access.
you can achieve your request using the script below:
LOAD * INLINE [
ACCESS, USERID, PASSWORD, NTNAME, USERGROUP
USER, *, *, DOMAIN1\PETER, G1
USER, *, *, DOMAIN\MAX, G2
ADMIN, TEST, TEST, *, *
View solution in original post
Thanks a lot for the quick response!
I dont remember that one has to use PASSWORD and NTNAME in the QlikSense sectionaccess. Aren't they used in QlikView?
What is NTNAME ?
Section Access fields are a bit different in Sense.
However NTNAME is the windows domain user account or even the windows local user account.
Section Access is for Data level security.
QMC security is not.
You'd have to do it manually as you did, associate an NTName (USERID) with a group/value.
What you did originally is correct. There seem to be no other way I know of.
please close this thread if you think has been answered.
I´d say it should be possible.
Within the script you can read custom properties via the REST connector interface.
Then you can modify the read data and put it in the section access table.
Not tested, but 99% sure it would work. I only would recommend to capsule this part in an external QVS script file if users/developers should not be able to get access information of all users.