topic Create a complex Row Level Access on a QlikView report. in QlikView

Create a complex Row Level Access on a QlikView report.

Anonymous — Wed, 25 Nov 2020 16:16:04 GMT

Hi!

I´m trying to apply a little complex type of Security Access into my QlickView report.

I have four columns of data:

Employee	Country	Salary	Supervisor
John	USA	4555	Kevin
Kevin	Canada	3425	Maria
Peter	USA	6000	Carter
Carter	USA	1345	Estela
Maria	Argentina	9000	Kevin
Dolores	Brazil	3456	Mike
Estela	Colombia	7654	Kevin
George	USA	2866	Mike
Mike	Canada	3333	Estela
Ruben	Argentina	1234	Estela
Carlos	Colombia	7689	Mike

On my report each USERID is a Supervisor and I need that each USER (Supervisors) can see the data (Salary, etc.) of all the people of his Country and also the information of their supervised people.

For example: USERID "Kevin" should see all the info of people of USA (John, Peter, Carter and George) AND the info of their supervised (María and Estela).

I´ve created this Access file but it doesn´t works.

ACCESS	USERID	COUNTRY	EMPLOYEE
ADMIN	ADMIN	*	*
USER	Kevin	USA
USER	Kevin		Maria
USER	Kevin		Estela
USER	María	Argentina
USER	María		Kevin
USER	Carter	USA
USER	Carter		Peter
USER	Estela	Colombia
USER	Estela		Carter
USER	Estela		Mike
USER	Estela		Ruben
USER	Mike	Canada
USER	Mike		Dolores
USER	Mike		George
USER	Mike		Carlos

There is a way to apply this type of Access Level?

I attach the files if you can try.

Thanks!

Re: Create a complex Row Level Access on a QlikView report.

vishweshwarisun — Thu, 03 May 2018 12:28:39 GMT

this thread will help you

row level security, how to?

Re: Create a complex Row Level Access on a QlikView report.

Anonymous — Thu, 03 May 2018 12:30:05 GMT

But that is for Qlik Sense

Re: Create a complex Row Level Access on a QlikView report.

Anonymous — Thu, 03 May 2018 12:45:50 GMT

Also on that Example, it uses a simple value per column as filter. In my case, I need to filter two or more values per column (Employee e.g).

Re: Create a complex Row Level Access on a QlikView report.

Miguel_Angel_Baeyens — Thu, 03 May 2018 13:52:13 GMT

Filtering by two or more values will work all right as long as the premises for the section access table apply:

Only one reduction value per line in the section access table, so for all possible combinations there must be one line for each
When using "*", all values for such field must be specified within the section access table (regardless how the field in the data model looks like). In the section access table, "*" does not mean "all possible values"
Field values and field names are UPPERCASE

Based on your example, for the case of Kevin, there must be a line for each combination of country (including employee's) AND employee:

ACCESS, USERID, COUNTRY, EMPLOYEE

USER, KEVIN, USA, KEVIN

USER, KEVIN, USA, JOHN

USER, KEVIN, USA, PETER

USER, KEVIN, USA, CARTER

USER, KEVIN, USA, GEORGE

USER, KEVIN, CANADA, KEVIN

USER, KEVIN, COLOMBIA, ESTELA

USER, KEVIN, ARGENTINA, MARIA

etc...

Because what section access does is the same as when having a selection in the file, you click on File > Reduce Data > Keep Possible Values

So if you select KEVIN in the field Supervisor, all values in white in the fields Employee and Country must be included in the section access.

One way of simplifying this is creating a link table between a key value in one field in the section access table (think of a concatenated key of country & '|' & employee, for example) and another with all possible values.