Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

Announcements
Qlik Analytics Tour 2020 Online. Begins August 10th. Register Today
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Creator II
Creator II

Section access query

Hi ALL,

My reduction field in section access has empty value as well as NULL values.

How to resolve this situation to work the section access ?

Regards,

Mahamed

9 Replies
Highlighted
Specialist III
Specialist III

Re: Section access query

You can do this with two ways.

1.- Unselect Strict Exclusion

2.- Join your access section table with all possible values when they are null

Thanks!

Highlighted
MVP
MVP

Re: Section access query

Normally records with null reduction fields will not be visible to any user. They may be visible to admins if strict exclusion is unchecked.

I suggest that some analysis is required to determine the best approach to handling these null value fields before adding them as reduction field(s).

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
Highlighted
Creator II
Creator II

Re: Section access query

Hi Manuel,

One Query -

While using section access with some field reduction in script then it is always necessary, to

make that field in upper case in data model ?

If Yes, then after changing that field in upper case then all of its values will reflect in upper case in final app and if again some user wants to see that field value in lower case then?

Regards,

Mahamed

Highlighted
Specialist III
Specialist III

Re: Section access query

Hi mahamed,

Standard fields on section access, like USERID, PASSWORD,... must be on uppercase. Reduction fields must be equal as your model field names.

If your reduction field is Country, on model must be Country.

The best way is change the field name on Section Access, with rename o with 'as' when you load your section access.

Kind regards.

Highlighted
Creator II
Creator II

Re: Section access query

Thank you Manual.

One more query -

- Generally, if the section access has been applied on Country.

- I am managing the section access using excel file.

- And as we all know, if we want to apply the section access on multiple values from Country for single user

  then we will need to add the separate line.

- So just to avoid adding separate line, is there any way to implement the section access on multiple Country values for    single user in single line ?

Regards,

Mahamed

Highlighted
Contributor III
Contributor III

Re: Section access query

Hi,

First handle this null in data level like replace some flag. Use the flag in section access file to link  and then use data reduction concepts.

Highlighted

Re: Section access query

Try like this, replace the null and blank values with a arbitrary values like NA and use the same in the data reduction . So that Admin will have access for all the data and rest will have access only for the data in data reduction field 

Highlighted
Specialist III
Specialist III

Re: Section access query

Hi mahamed,

There is no way to do it, you need one line by Country by User.

Regards!

Highlighted

Re: Section access query

In your original post, you mentioned that your Section Access should work with empty or NULL values. You can translate them on both sides into a text string (which does not clash with real values) like '*EMPTY*'.

In a later post you asked how you can avoid that users are confronted with dimension values in all upper case. When loading link field data in Sectiojn Application, create two fields in the same table, like

Section Application;

Data:

LOAD ...

     Upper(Country) AS COUNTRY, // Will link to section access

     Country, // Will be dimension/selection field

:

FROM ...,

And a third question somewhere was about how to avoid duplicate section access lines for users with multiple link values. There are a number of approaches available to you:

  1. Use a separate link table in Section application that reads from the same source as Section Access. That table will expand a single link field value (e.g. the User ID) into the different countries. Your section access table will not link via Country anymore but simply by way of a copy of the User ID. Result:; a single line per user in Section Access
  2. Define a grouping field that groups countries in regions. For example, Sales managers may be responsible for well-defined world regions like North-America, EMEA, Pacific, ... These you can define as a link table in Section Application. Each Section access entry will need a single region value to connect to multiple countries
  3. OTOH, if you are reading security definitions from an Excel, then why worry about multiple lines in Section Acess? You will never see them...

Best,

Peter