Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More

QlikView Section Access Examples

cancel
Showing results for 
Search instead for 
Did you mean: 
Colin-Albert

QlikView Section Access Examples

Last Update:

Oct 7, 2022 9:22:04 AM

Updated By:

Sonja_Bauernfeind

Created date:

Feb 24, 2014 6:54:29 PM

Attachments

The  attached file SectionAccess.zip contains several example documents that show how Section Access can be used to restrict access to specific users and to specific data.

 

This is not a guide on how to use Section Access, but instead shows some of the common errors and how to avoid them.

 

An excellent guide to Section Access can be found here http://community.qlik.com/docs/DOC-1853

Marcus_Sommer has accumulated a comprehensive list of Section Access Resources in this document Section Access

 

These examples will require a licenced copy of QlikView to open them, so they not suitable for users with QlikView Personal Edition.

 

The example documents will ask for a username and password to open them and set the Section Access permissions. The following usernames and passwords can be used to open the documents and see the different functionality with Section Access. When changing from one user to another, you must close QlikView before you can open a document as another user.

UserID,  Password

ADMIN,  ADMIN

JOHN, JOHN

MARY,  MARY

PETER,  PETER

SIMON,  SIMON

 

You can view the load script to see how the Section Access and data is configured.

 

Section Access Example 1

This document attempt to restrict access to a list of named users, but this fails as the section access field names are not set as UPPERCASE in the script.

 

Section Access Example 2

The app is now correct and prompts for a username and password before users can access the data.

 

Examples 1 & 2 use the Basic section access data from SectionAccess.xlsx

 

Access,  UserID,  Password

USER,  USER,  USER

ADMIN,  ADMIN,  ADMIN

USER,  JOHN,  JOHN

USER,  MARY,  MARY

USER,  PETER,  PETER

ADMIN,  SIMON,  SIMON

 

Section Access Example 3

The data is restricted so users can only access the Cost Centre data as listed in the Cost Centre  column in Section Access.

Access,  UserID,  Password,  CostCentre

USER,  USER,  USER,  *

ADMIN,  ADMIN,  ADMIN,  *

USER,  JOHN,  JOHN,  A

USER,  MARY,  MARY,  B

USER,  PETER,  PETER,  C

ADMIN,  SIMON,  SIMON,  A

 

Section Access Example 4

This adds extra DUMMY rows to the section access table so the * entries can now access all cost centres.

Access,  UserID,  Password,  CostCentre

USER,  USER,  USER,  *

ADMIN,  ADMIN,  ADMIN,  *

USER,  JOHN,  JOHN,  A

USER,  MARY,  MARY,  B

USER,  PETER,  PETER,  C

ADMIN,  SIMON,  SIMON,  A

DUMMY,  DUMMY,  DUMMY,  D

DUMMY,  DUMMY,  DUMMY,  E

DUMMY,  DUMMY,  DUMMY,  F

DUMMY,  DUMMY,  DUMMY,  G

DUMMY,  DUMMY,  DUMMY,  H

 

Note – you cannot open the document as user DUMMY because DUMMY is an invalid Access value, only ADMIN and USER entries are allowed to open the document.

 

Section Access Example 5

This adds Region to the restrictions as well as CostCentre, but the restriction on Region fails as the

region fieldname is not UPPERCASE.

 

Access,  UserID,  Password,  CostCentre,  Region

USER,  USER,  USER,  *,  *

ADMIN,  ADMIN,  ADMIN,  *,  *

USER,  JOHN,  JOHN,  A,  North

USER,  MARY,  MARY,  B,  South

USER,  PETER,  PETER,  C,  East

ADMIN,  SIMON,  SIMON,  A,  North

ADMIN,  SIMON,  SIMON,  A,  East

DUMMY,  DUMMY,  DUMMY,  D,  North

DUMMY,  DUMMY,  DUMMY,  E,  South

DUMMY,  DUMMY,  DUMMY,  F,  East

DUMMY,  DUMMY,  DUMMY,  G,  West

DUMMY,  DUMMY,  DUMMY,  H

 

Section Access Example 6

The Region fieldname is uppercase, but the restriction on Region still fails as the region data is not UPPERCASE.

 

Section Access Example 7

The Region restriction now works by loading the region data into a second field named REGION_SA and forcing the data in REGION_SA to UPPERCASE.

Version3 - The Region field has been removed from the Section Access table. This fixes the error identified by kanhomcake (March 27 2014).

 

Hopefully this will help avoid some of the basic errors that can be made when implementing Section Access.

 

Colin Albert.

Labels (1)
Comments
Anonymous
Not applicable

Hi Colin,

I cannot open the Section Access 7  example with any of the User Names.  Can you please advise how I can view this qvw?  Thank You.

Anonymous
Not applicable

hi albert ,

  i have a question if in case for user MARY there is no South data then how to over come this time actually am getting "access denied" error, when open the qvw file if user related data is not available

please suggest me

Anonymous
Not applicable

Good overview. It would have been a complete guide if the explanation on group restrictions were elaborated.

ZoeM
Specialist
Specialist

Hey Colin, I know this thread a little old, but I would like to find out how to use Section Access for a dynamic field such as Year. I want to restrict certain users to seeing ONLY Current Year and previous years and NOT future years (upcoming planned sales trend analyses etc).

Is this possible and how would I define the Section Application?

tincholiver
Creator III
Creator III

Hello everyone, I make the following query.
List in an excel the allowed fields for each user as explained, but I ran into a problem, and it is as follows:
one of the fields called branch, is not in all the tables of the data model, therefore all the information contained in those tables are not shown in the graphs, how can I solve this problem? ideas?

thank you!

cooper_yonk
Contributor III
Contributor III

I know this is an old post but we use qlikview 12.  If I wanted to use  this method to reduce the data in an app from a large binary loaded datamodel, how would I do that?

I dont need to be able to restrict access per user, the end goal is to have an app with reduced data in it based on a field eg Data Type = "Local"

Any help appreciated

Version history
Last update:
‎2022-10-07 09:22 AM
Updated by: