Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Fields reduction in list boxes-Section Access

Hi All,

I am using list boxes in a sheet to display various measures.Can the fields in the list boxes can be restricted depending on the user login using section access.Please help me to sort out this problem

Thanks in advance

7 Replies
Not applicable
Author

Is this type of reduction of data possible?

Please Reply Fast

adamwilson
Partner - Creator
Partner - Creator

This is straight from the reference manual, it shows exactly how to hide fields and hide rows, hope it helps:

Dynamic Data Reduction

First of all, fields (columns) can be hidden by the use of the system field OMIT.

Secondly, records (rows) can be hidden by linking the Section Access data with the real data: The selection

of values to be shown/excluded is controlled by means of having one or more fields with common names in

section access and section application. After user login QlikView will attempt to copy the selections in

fields in section access to any fields in section application with exactly the same field names (the field

names must be written in UPPER CASE). After the selections have been made, QlikView will permanently

hide all data excluded by these selections from the user.

In order for this procedure to take place, the option Initial Data Reduction Based on Section Access on the

Document Properties: Opening page must be selected. If this feature is used in documents that are to be distributed

by other means than via QlikView Server, the option Prohibit Binary Load on the same page of

the Document Properties must be selected in order to maintain data protection.

Note!

Example:

    section access;

    load * inline [

    ACCESS, USERID,REDUCTION, OMIT

    ADMIN, ADMIN,*,

    USER, A,1

    USER, B, 2,NUM

    USER, C, 3, ALPHA

    ];

    section application;

    T1:

    load *,

    NUM AS REDUCTION;

    load

    Chr( RecNo()+ord(‘A’)-1) AS ALPHA,

    RechNo() AS NUM

    AUTOGENERATE 3;

   

The field REDUCTION (upper case) now exists in both section access and section application (all field

values are also upper case). The two fields would normally be totally different and separated, but if the Initial

Data Reduction Based on Section Access option has been selected, they will link and reduce the

number of records displayed to the user.

The field OMIT in section access defines the fields that should be hidden from the user.

The result will be as follows:

User A can see all fields, but only those records connected to REDUCTION=1.

User B can see all fields except NUM, and only those records connected to REDUCTION=2.

User C can see all fields except ALPHA, and only those records connected to REDUCTION=3.

Not applicable
Author

Thanks Adam,

It was helpful. But can i reduce the data present in the list boxes using OMIT depending on the user.If so how can i do that?

adamwilson
Partner - Creator
Partner - Creator

OMIT hides the column from the user.

If you just want to show certain values within a field you have to define this within the section access. Look at the field REDUCTION in the example.

khadeer
Specialist
Specialist

U can restrict in data, sheet n document level

PFA. It will help u

Not applicable
Author

How do you not reduce values in the data?

I currently have a document with Section Access and on the front-end I am suppose to see all values displayed in the listboxes in the document. I am not seeing all the values but a reduced list. I already know that due to not being data available for the values, it will not be available but still the values should be present and should be grayed out. This is not occuring.

Any suggestions on how to resolve this issue?

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

Section Access will remove the values completely from the user - this is 99.9% of the time what you will want to do.  What you are describing is like you want to apply a selection on a user opening the document that you then lock that selection.

I wouldn't advise this approach.