Skip to main content
Solved

Hiding expression fields via a layout procedure is no longer possible

  • October 23, 2019
  • 3 replies
  • 130 views
K.Bakkenes
Captain
Forum|alt.badge.img+9

In SF 2019.1 it's no longer possible to hide/display expression fields via a layout procedure. The checkboxes (under ‘Subjects’)  are disabled. All existing expression fields (fortunately) still have checked checkboxes. (see screenshot)

Why is this CHG made in SF 2019.1? Based on an issue or because of performance? What is the alternative solution to hide/display expression fields via a layout procedure?

This CHG is a problem for us because we often use expression fields to display actual data via the underlying query or hide/display the fields based on the filling of other fields/tables.

 

 

Best answer by Jeroen van den Belt

Thank you for your question. We agree that is should be possible to set the layout type output for expression columns. This is already fixed in the SF 2019.2. Do you think this should be hotfixed for the 2019.1?

View original
This topic has been closed for comments

3 replies

Jeroen van den Belt
Administrator
Forum|alt.badge.img+9

Thank you for your question. We agree that is should be possible to set the layout type output for expression columns. This is already fixed in the SF 2019.2. Do you think this should be hotfixed for the 2019.1?

K.Bakkenes
Captain
Forum|alt.badge.img+9
  • K.BakkenesCaptain
  • Author
  • Captain
  • 41 replies
  • October 29, 2019

A hotfix would be nice! That would prevent us from creating queries on the SF database to set the layout checkboxes.

Jeroen van den Belt
Administrator
Forum|alt.badge.img+9

A hotfix is created, see: https://community.thinkwisesoftware.com/updates-and-releases-31/hotfix-sf-2019-1-layout-type-output-for-expression-columns-782

Please let me know if this solves your situation.

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings