Within Method's stock screens, a lot of information is displayed, and it is a common request to remove information not applicable from the screen.
For example, in the below Invoice screenshot, there is a dropdown for Location. If your company has no need for this information, you may want to delete it.
However, deleting it could be problematic: that field could be integral to an action workflow.
Instead of deleting, it is best practice to hide it instead. You can hide fields, objects, and whole sections.
When you hide a control, actions will still be able to reference it, but it will not show up on the screen.
📌 Note: If an object is already set to hidden, but shows up on the screen, this means an action set shows this object based on certain conditions.
By selecting the object, and scrolling to the bottom of its properties, you will find a section called References.
This will show the events that reference that object. Searching through those events, you will find the action that shows the object.
Hiding a control
Customize the screen with the control you wish to hide.
Select the control. This will display its properties on the right. Remember, you can also select whole sections and make them hidden as well.
Change the control's load state to Hidden.
Repeat as necessary to other controls on the screen. If the controls are all in one section, consider hiding that whole section.
Save the screen.
The controls will no longer show up on the screen!
Group and Hide Multiple Controls
There may be times when you want to hide a lot of controls, or a control is made visible again via an action.
For example, the DueDateEnd field in the New Activity screen will become visible if a user selects a meeting activity type.
In these cases, it would be better to:
Ceate a brand new section and name it SectionHidden.
For its Load State, change it to Hidden.
Add a few rows or columns to SectionHidden, and then drag all the controls you want invisible into this new section.
The section invisibility will override the visibility of the controls within it, so in this case, it will not matter if an action makes a control visible.
Furthermore, this is easier to do if you have a lot of controls and don't want to individually set each one to hidden.