When customizating a screen/form example End Activity, and there are standard fileds not used.
Is it best to mark then visible false, or move them off of the group?
Streamlining can be a two edged sword. On one hand, you’ve made the screen easier to use/read. On the other hand, your users will not see features they may need in the future. I’ve seen plenty of customizations that have been streamlined, but then they created UD fields because they didn’t know the field/feature already existed.
To answer your question, you will need to move them if you want to consolidate the screen. Also, Customization Maintenance will complain if the field overlaps another or is outside the visible range.
Jason’s point is valid.
However, if you do decide to hide controls, you will find that with some screens (assuming you are talking about the Classic interface), that setting Visible = false in your customization gets overridden on form load. In those cases we’ve had to move them to a location that is outside the visible area.
1 Like
Thank you for the responses.
Understanding that is it s two edge sword.
I believe in the past we have moved the field off of the visible group. Before we go to add UD fields we review the Data Dictionary, and look at screens in base mode.
Thank you
