SlideShare a Scribd company logo
1 of 3
Download to read offline
QlikView Section Access Examples
The 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
The examples all require a licenced copy of QlikView to open them.
These examples are 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 documenmts
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 attemps to restrict access to a list of named users, but this fails as the section access
filed names are not set as UPPERCASE in the script.
Section Access Example 2
The app is now 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.
Hopefully this will help avoid some of the basic errors that can be made when implementing Section
Access.
Colin Albert.

More Related Content

Similar to Qlik view section access examples

76829060 java-coding-conventions
76829060 java-coding-conventions76829060 java-coding-conventions
76829060 java-coding-conventions
slavicp
 
SOP_ERP_AdministrationModule
SOP_ERP_AdministrationModuleSOP_ERP_AdministrationModule
SOP_ERP_AdministrationModule
Sunil Mukadam
 
Design Document Sample
Design Document SampleDesign Document Sample
Design Document Sample
Steve Smith
 
eDocs Rename Sub Folder
eDocs Rename Sub FoldereDocs Rename Sub Folder
eDocs Rename Sub Folder
Mohammed Golam
 
CICONF 2012 - Don't Make Me Read Your Mind
CICONF 2012 - Don't Make Me Read Your MindCICONF 2012 - Don't Make Me Read Your Mind
CICONF 2012 - Don't Make Me Read Your Mind
ciconf
 
5 User Mgmt in Drupal
5 User Mgmt in Drupal5 User Mgmt in Drupal
5 User Mgmt in Drupal
Wingston
 

Similar to Qlik view section access examples (20)

SMS.pptx
SMS.pptxSMS.pptx
SMS.pptx
 
A deep dive into accessible names
A deep dive into accessible namesA deep dive into accessible names
A deep dive into accessible names
 
76829060 java-coding-conventions
76829060 java-coding-conventions76829060 java-coding-conventions
76829060 java-coding-conventions
 
OOP C++
OOP C++OOP C++
OOP C++
 
SOP_ERP_AdministrationModule
SOP_ERP_AdministrationModuleSOP_ERP_AdministrationModule
SOP_ERP_AdministrationModule
 
Les25
Les25Les25
Les25
 
C#Portfolio
C#PortfolioC#Portfolio
C#Portfolio
 
OOP.ppt
OOP.pptOOP.ppt
OOP.ppt
 
Design Document Sample
Design Document SampleDesign Document Sample
Design Document Sample
 
Unit4 NMA working with user accounts WINDOWS SERVER 2008
Unit4 NMA working with user accounts WINDOWS SERVER 2008Unit4 NMA working with user accounts WINDOWS SERVER 2008
Unit4 NMA working with user accounts WINDOWS SERVER 2008
 
Unit+eight+ +ubuntu+security
Unit+eight+ +ubuntu+securityUnit+eight+ +ubuntu+security
Unit+eight+ +ubuntu+security
 
Unit+eight+ +ubuntu+security
Unit+eight+ +ubuntu+securityUnit+eight+ +ubuntu+security
Unit+eight+ +ubuntu+security
 
Riding Rails 4
Riding Rails 4Riding Rails 4
Riding Rails 4
 
eDocs Rename Sub Folder
eDocs Rename Sub FoldereDocs Rename Sub Folder
eDocs Rename Sub Folder
 
Does DITA need XML? Lightweight DITA and HTML5
Does DITA need XML? Lightweight DITA and HTML5Does DITA need XML? Lightweight DITA and HTML5
Does DITA need XML? Lightweight DITA and HTML5
 
CICONF 2012 - Don't Make Me Read Your Mind
CICONF 2012 - Don't Make Me Read Your MindCICONF 2012 - Don't Make Me Read Your Mind
CICONF 2012 - Don't Make Me Read Your Mind
 
5 User Mgmt in Drupal
5 User Mgmt in Drupal5 User Mgmt in Drupal
5 User Mgmt in Drupal
 
OBIEE 11g: Configuring LDAP Server
OBIEE 11g: Configuring LDAP Server  OBIEE 11g: Configuring LDAP Server
OBIEE 11g: Configuring LDAP Server
 
04 Html Form Get Post Login System
04 Html Form Get Post Login System04 Html Form Get Post Login System
04 Html Form Get Post Login System
 
Partitioning IBM Connections Cloud Administration
Partitioning IBM Connections Cloud AdministrationPartitioning IBM Connections Cloud Administration
Partitioning IBM Connections Cloud Administration
 

Qlik view section access examples

  • 1. QlikView Section Access Examples The 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 The examples all require a licenced copy of QlikView to open them. These examples are 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 documenmts 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 attemps to restrict access to a list of named users, but this fails as the section access filed names are not set as UPPERCASE in the script. Section Access Example 2 The app is now 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
  • 2. 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.
  • 3. 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. Hopefully this will help avoid some of the basic errors that can be made when implementing Section Access. Colin Albert.