Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Section Access on Drill down

Hello Everyone,

I have question on section access. My app has Location dimension and I need give user different access on each level and below on the location dimension.

Please see attached QVW for more detail.

The requirement is:

USER1 has The World privilege and he can access The World and below location

USER2 has Africa privilege and he can access any location belong to Africa

USER3 has South Africa privilege and he can access any location to South Africa

...

and so on.

Please help me on this section access set up.

Thank you very much in advance.

Best regards,

Dust

(Very important note: this qvw is based on Herric Cronstrom's online posting)

1 Solution

Accepted Solutions
hic
Former Employee
Former Employee

Today you have

Section Access;
LOAD * INLINE [
ACCESS, USERID, PASSWORD
ADMIN, ADMIN, ADMIN
USER, USER1, USER1
USER, USER2, USER2
USER, USER3, USER3,

  ...

Section Application;
LOAD * Inline [
USERID, Tree
USER1, The World
USER2, Asia
USER3, South Africa,

   ...

But you should have

Section Access;
LOAD ACCESS, USERID, PASSWORD, Upper(Tree) as TREE
INLINE [
ACCESS, USERID, PASSWORD, Tree
ADMIN, ADMIN, ADMIN, The World
USER, USER1, USER1, The World
USER, USER2, USER2, Asia
USER, USER3, USER3, South Africa,

...

Section Application;
[Trees]:
Hierarchy (TreeID, TreeParentID, Tree)
LOAD NodeID as TreeID,
ParentID as TreeParentID,
NodeName as Tree,
Upper(NodeName) as TREE

  ...


HIC

View solution in original post

8 Replies
Oleg_Troyansky
Partner Ambassador/MVP
Partner Ambassador/MVP

Basically, to implement multi-level Security, you should create a number of custom security fields in Section access and then associate each field to a different field in your data model - for example, one field would be associated with Continents, another field - with Regions, then Countries, etc...

I'm not sure if it's possible to arrange security levels based on a true Hierarchy where the number of nodes and the depth of the hierarchy is unknown. Perhaps we need hic‌ to post a white paper on that...

cheers,

Oleg Troyansky

Check out my new book QlikView Your Business: An expert guide to Business Discovery with QlikView an...

Not applicable
Author

Thank you - Oleg.

Potentially, we may need add or delete location in the future and want section access can automatically done based on location exist.

Congratulations on your new book. Do you have e-book version?

Best regards,

Dust

Oleg_Troyansky
Partner Ambassador/MVP
Partner Ambassador/MVP

Well, if you associate your security fields with regular data fields, and some of the locations get deleted, then the access to these locations will disappear automatically. For new locations, you will have to specify who should have access to them (higher levels of the hierarchy will get access automatically).

Regarding the book - thanks! Yes, Kindle, iBooks and all other commercial book formats are available. Amazon sells Kindle, of course, but I saw other formats in other on-line stores.

hic
Former Employee
Former Employee

This is certainly possible. See Authorization using a Hierarchy

HIC

Not applicable
Author

Thank you very much - HIC.

Read your posting again and modify this apps and it looks right now. Please see attached QVW.

Appreciate your very intelligent solution.

Not applicable
Author

Henric,

I am studying your posting on hierarchy.

I have another question:

Is there a way to generate NodeID and ParentID based on a existing Hierarchy Dimension.

Thank you very much for your comments.

best regards,

Dust

hic
Former Employee
Former Employee

Today you have

Section Access;
LOAD * INLINE [
ACCESS, USERID, PASSWORD
ADMIN, ADMIN, ADMIN
USER, USER1, USER1
USER, USER2, USER2
USER, USER3, USER3,

  ...

Section Application;
LOAD * Inline [
USERID, Tree
USER1, The World
USER2, Asia
USER3, South Africa,

   ...

But you should have

Section Access;
LOAD ACCESS, USERID, PASSWORD, Upper(Tree) as TREE
INLINE [
ACCESS, USERID, PASSWORD, Tree
ADMIN, ADMIN, ADMIN, The World
USER, USER1, USER1, The World
USER, USER2, USER2, Asia
USER, USER3, USER3, South Africa,

...

Section Application;
[Trees]:
Hierarchy (TreeID, TreeParentID, Tree)
LOAD NodeID as TreeID,
ParentID as TreeParentID,
NodeName as Tree,
Upper(NodeName) as TREE

  ...


HIC

Not applicable
Author

HIC,

Appreciate your help. I just saw your answer here and it's big help on my section access setup.

Thank you again.

Best regards,
Dust