Skip to main content

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
Welcome to Qlik Community! Check out our new navigation! FIND OUT MORE

Change how omitted fields based on section access are handled in the GUI in Qlik Sense

jlp
Employee
Employee

Change how omitted fields based on section access are handled in the GUI in Qlik Sense

In Qlik Sense there is a big risk that the GUI is completely unusable if there is a field that is omitted based on section access.

The users that have a field omitted - for example Patient Name - can end up in "deadlocks" if for example the field is used as an alternate dimension.

When selecting the alternate dimension the complete visualization will render as "Invalid" and the drop down for getting back to an available dimension is not accessible anymore. Hence, there is no way for the user to get back to a working version of the visualization (without ending the session and open the app again).

Tables where the omitted field is used will render as "Invalid" instead of just having the field column set to null in all the values (QlikView still let's the user see the table but the column is blank).

It is only the content of the field that is sensitive - not the visualizations themselves.

Ideally, this should be rendered differently.

3 Comments
AndrewMcIlwrick
Luminary Alumni
Luminary Alumni

Wow - this is bad

simonaubert
Partner - Specialist II
Partner - Specialist II

@jlpHello. Can you provide some screenshots please?

Ian_Crosland
Employee
Employee
 
Status changed to: Open - Collecting Feedback