Skip to main content
J
JensN.1-Visitor
1-Visitor
December 19, 2017
Question

How to hide fields in an item, but have them visible in queries, reports etc.

  • December 19, 2017
  • 1 reply
  • 1975 views

Since version 11 (maybe earlier, we switched from version 10.7 to 11), the relevance rules for fields are evaluated correctly. Since then, the values of a field are no longer displayed in queries if the field is configured as invisible in the item.

Up to at least version 10.7, this was not the case, and we were able to hide fields with computations in the item, but still display the values in queries. We would like to continue to do this, especially since users are used to being able to read these values in queries. Does anyone have any idea how to do this?

kind regards, Jens

1 reply

M
MichaelChatel5-Regular Member
5-Regular Member
December 19, 2017

Jens,

 

Were you using (or would it make more sense now), to make use of the "Visible When" option, on the item presentation templates themselves, for each field, or if you have fields located within a grid?  It seems like you possibly just want the hide/donothide functionality, for when the fields are presented on the item display?

 

 

J
JensN.1-VisitorAuthor
1-Visitor
December 20, 2017

Hi Michael,

 

we're doing this right now. At the moment we're using three different methods to hide fields in items:

 

1. using the relevance rule from the field itself

2. using the "visible when" function for one field

3. using the "visible when" function for a whole table grid

 

However, the last two points always have a different field as a trigger, which in turn is suppressed using relevance rules, and these rules are also applied to the query view.

 

Is there another way to trigger this "visible when" function?

 

Kind regards, Jens

J
JensN.1-VisitorAuthor
1-Visitor
December 20, 2017

We have found a quite cumbersome workaround: A new field is created, which must not be listed under "Visible fields" in an item, or it must not be used in an item at all. For example this field is called "Invisible_Flag". Another field called "Invisible_Flag_except_for_Admins" has also been created, but this flag will be added to the item. This second field contains relevance rules that define visibility for admins only.

A table grid with contents, which the users should not see in the item, has been created and is assigned with the flag "Invisible_Flag" via the "visible when" function. This means that users can still use these fields in queries even though they cannot see them in the item.

But since also admins can't see this table grid anymore, the complete grid has been copied and is pasted in another tab of the item. Here the grid is switched to invisible for users via the flag "Invisible_Flag_except_for_Admins". This limits the visibility to administrators.

Both specifications have an effect. This is a workaround for the new inheritance of relevance rules and both administrators and normal users can see exactly what they need.

 

Maybe this helps anone too...

 

Kind regards, Jens

Terms & ConditionsCookie settingsAccessibility statement