Qlik Snippets: Self-service: Controlling Visibility of Fields

[@Gustjps]

You Save-me ! Thanks !

[@MrCalifornia]

This can also be accomplished by doing: Tag Fields [Hidden Field 1], [Hidden Field 2], [Hidden Field 3] with $hidden; I usually use a combination of the two. Hide Prefix % with the key fields and Tag Fields $hidden with other fields I want to not show in Self Service.

[@GuyInaQ]

Thanks Andy - I updated the post with your suggestion - I like this one best!

[@DrDeadLion]

I doubt it can be called a security feature. Just being hidden in the field lists does not mean the field can't be typed manually.

[@GuyInaQ]

Hello DrDreaLion - you are correct. What is mentioned in this video is one approach to control visibility and limit the number of additional fields that are displayed in field lists. A true security feature would be to use Qlik Dynamic Data Reduction / Section Access to control what is actually available (field level, row level etc.) based on the user, role or custom security rule. Let us know if you have any more questions and be sure to join us in the Qlik Community where we can better answer your questions.

[@eliransanor137]

Just a quick note to this one, the above *does not* protect the data. it's just hiding the field name from the list. For instance, when using $Field or $Table (system fields), it won't popup in the list, but it's usable in the model.

[@GuyInaQ]

Hi Eliran - exactly yes - if you want to protect the data columns and rows - you would use Dynamic Data Reduction or Section Access - this method is just to make the field lists more manageable for the users and the interface.

[@jonasfurtado4057]

Hi Mike, I just tested this feature. In the above example, say if I use Order ID field to create any visual with measure say count(Order ID) and then publish the App, I found that the visual will not show data for the count(Order Id), although it hides the field for the self service. Any thoughts on how I can have the data intact in the visuals built using the hidden fields?

[@jonasfurtado4057]

MY bad. I take my words back :-). The data is available in the dashboard for calculation. So in the dashboard I need to refer to the hidden field with the prefix i.e. count(%Order ID) in this case

[@toulasantha]

Hey Mike What about section access for more granular level control ? Please make a video on that topic too.. Thanks

[@QlikOfficial]

Good idea - We will let Mike know - we appreciate your comment and support!