topic Re: Section Access in QlikView

Section Access

jyothish8807 — Fri, 12 Feb 2016 07:36:34 GMT

Hello All,

I am trying to implement a section access logic, also looking for a solution which should not impact the opening time of the application much.

Below is the scenario:

Country	Category	Sales
A	Data1	100
B	Data1	21
C	Data1	23
D	Data1	12
A	Data2	34
B	Data2	21
C	Data2	45
D	Data2	21

So, suppose when a user "Jyothish" logs in, he should have access to see Sales data for Country "A" and where category is "data 1" , but he should have access to see sales of all countries where Category is "Data2".

So output data should be like this, i mean the data he should be able to see:

Country	Category	Sales
A	Data1	100
A	Data2	34
B	Data2	21
C	Data2	45
D	Data2	21

Thanks in advance.

Regards

Re: Section Access

Fri, 12 Feb 2016 07:46:26 GMT

Hello Jyothish,

I don't know if the impact is big or not but reader what you need you should use data reduction with two fields specifying the combinations of Country and Category that each user would be able to see.

section access - multi-field data reduction

Re: Section Access

Anonymous — Fri, 12 Feb 2016 07:49:44 GMT

Did you check this? Clean and neat explanation ...

QlikView Section Access Examples

Introduction to Section Access

A Primer on Section Access

Re: Section Access

avinashelite — Fri, 12 Feb 2016 07:59:23 GMT

try like this

in section application use the NTNAME and in the section application use only the Country column not the Category so that the data will get reduce according to the Country but not the catagory

SECTION ACCESS;

LOAD ACCESS,

NTNAME

from

table;

SECTION APPLICATION;

LOAD

NTNAME

Country;

Note the Country column should be in the same name as your data model

Hope this helps you

Re: Section Access

Chanty4u — Fri, 12 Feb 2016 08:02:33 GMT

always use UPPER ( fieldname) in section access.

Re: Section Access

jonathandienst — Fri, 12 Feb 2016 08:16:44 GMT

This may also help to do more complex access control:

Generic keys

Re: Section Access

Mark_Little — Fri, 12 Feb 2016 08:20:35 GMT

HI,

Reading the requirements the above will help with the scripting the section access, but not for the access you are describing.

I reckon you will need to make a concatenate key between country and category and then give him the relvant access to right combinations.

Mark

Re: Section Access

jyothish8807 — Fri, 12 Feb 2016 08:22:45 GMT

Hi Avinash,

Thanks for your input. the solution you suggested a very generic one and it will work for only one country.

But in my case it a bit complicated.

Regards

Re: Section Access

kaushiknsolanki — Fri, 12 Feb 2016 08:27:09 GMT

Hi,

Have a look at the below link.

Basics for complex authorization

Hope this will help.

Regards,

Kaushik Solanki

Re: Section Access

jyothish8807 — Fri, 12 Feb 2016 08:28:11 GMT

Hi Mark,

Thanks for your suggestion, even i have done the same and its working for me.

But the challenge is it is effecting the opening time of the application.

Is there any easy way to do this, other than doing the concatenate key and other mappings.

In actual the scenario is very complex than what i have highlighted, there are multiple combinations.

Will applying the section access at publisher level will improve the performance of the application?

Regards

Re: Section Access

Mark_Little — Fri, 12 Feb 2016 08:36:56 GMT

Hi,

When i have done it in the past it has not been to bad for effecting the opening times. I would normally set it up as an access group, so i can try to minimize the amounts of combinations attached to the users.

Like below.

Access	NTNAME	AccessLevel
User	DOMAIN\USERNAME	IT

Then set up the groups.

AccessLevel	AccessKey
IT	AData1
IT	BData1

Mark

Re: Section Access

beck_bakytbek — Fri, 12 Feb 2016 12:59:26 GMT

http://www.youtube.com/watch?v=qMsTaFD3ql0

Re: Section Access

Peter_Cammaert — Fri, 12 Feb 2016 13:51:46 GMT

What impact on opening times are you talking about? Seconds? Minutes?

Data reduction always impacts the opening time, especially when having a complex data model with many rows. But it should be about the same as making selections in your document.

Best,

Peter