topic Re: User specific filters in QlikView

User specific filters

Wed, 04 Dec 2013 15:21:25 GMT

I want to show certain data selections for individual users when opening the Qlikview document.

If i load in a table showing which filters for each user eg two columns, user ID, Cust ID.

Then I add in an action of "select in field" for example with the field being the list box/crietira i intend to filter for them say customer id.

Using the search string how do i get back to the table eg if i can use the function OSuser( ) to find the login, how i can i get back to the selections i want from the table?

Re: User specific filters

matthias_v — Wed, 04 Dec 2013 15:30:06 GMT

Maybe you should consider setting up SECTION ACCESS in combination with the document setting (Initial selection based on section access) you see in the attached screenshot. I think this will do exactly what you are trying to do.

Re: User specific filters

Wed, 04 Dec 2013 15:36:36 GMT

if you have different profiles seeing different graphs you can play with actions and conditional display.

Jus build a specific tab for each set of users, if there are not many

If users must see same graphs with different data then it is better to use section access as Matthias told.

best regards

Chris

Re: User specific filters

Wed, 04 Dec 2013 15:46:30 GMT

Where is the link made between user login & selections?

Re: Re: User specific filters

matthias_v — Wed, 04 Dec 2013 16:05:12 GMT

Have you ever setup section access?

If not it would be something along the lines of:

Section Access;

Load * inline [

ACCESS,NTNAME, SECID

USER, userA, 1

USER, userB, 2

];

Section Application;

SecTable

Load

1 as SECID,

'Customer1' as CustomerID

Autogenerate 1;

CONCATENATE (SecTable)

LOAD

2 as SECID,

'Customer2' as CustomerID

Autogenerate 1;

This should be placed at the beginning of your script before the variables.

This example together with the setting i showed you, will have an initial selection for the NT-User userA on SECID = 1 (if i'm not mistaken) and because of the associative model, only the customer with CustomerID 'Customer1' will be a possible value.