Comments
If this is true, how could have this been missed before the Windows client was retired?...
Category: General
I totally support this request. The current behavior is absolutely inconsistent. In the Windows client a VISIBLE=FALSE property was interpreted as "InitialHidden" which gives the user the possibility to make it visible by customizing the page. However, in the WebClient it is interpreted differently, more like "disabled".
Please make the behavior consistent again or even better: give developers control by adding new values to control visibility like
"InitialHidden": Hidden by default. User can still unhide the control
"InitialVisible": Shown by default. User can still hide the control
"TRUE": Always shown, user can not hide it. This can be extremely important when working with multiple subpages that depend on each other via the subpagelink.
"FALSE": Never shown. User can not unhide the control. Useful for debugging scenarios.
Category: General
Moreover, it doesn't seem to be possible for a user to add a factbox back to a page if they hide it. (Without resetting their page customisation entirely.)
Category: General
Business Central Team (administrator)