Lets your company rename a field, hide it, change how it is entered, and reword or hide a list column. The changes apply to your screens only and do not change the product.
When to use it
- Your organisation calls something by a different name than the screen does, and staff keep asking.
- A field nobody in your business fills is cluttering a form.
- A list has a column your users do not need.
Before you start
Know which screen you want to change; you pick it from a list here. Only fields the product has opened up for tailoring appear. If a screen shows nothing, it is not that you lack rights: nobody has opened any of its fields for tailoring, and the page says so. That is a request for your administrator, and you cannot force it here.
Where to find it
Setup > System Customization > Form & Table Customization.
How it works
Pick a screen, then work through its fields one card at a time. Each card shows what the field is called and how it looks as standard, and what you have changed.
- Save writes your company's version. The standard is untouched and no other company is affected. Reset removes your version, and the field goes straight back to standard.
- A blank label box means "no change", not "no label". Clearing a box you had typed in brings back the standard wording; the field is not left without a name.
- Visible on form is one switch that covers adding, editing and viewing together. You cannot make a field appear only when adding a record and not when editing it.
- The type list only offers what the product allows for that field, and it is locked when nothing is allowed. That is a safety limit: not every field can sensibly be entered a different way.
- The validation tick saves the moment you tick it. There is no Save step for it and no confirmation. If it fails, the whole card list refreshes, so what you see is what actually took.
Changes reach your users the next time they load that screen. Hiding a field does not delete anything. Records that already have a value keep it, the value is still stored, and it comes back as soon as the field is shown again. So hiding can be undone in a way that deleting data cannot.
Tips and common mistakes
- Change one field, then go and look at the real screen. A mistake is much easier to see on the form than on the card.
- Hiding a field that people are required to fill does not remove the requirement. If a screen starts refusing to save after a change here, put the field back and check.
- Renaming a field does not rename it in reports, exports or this help, so keep the change small and obvious.
Related guides
Workflow Variants is where you choose an approval flow, and Report Overrides applies the same idea to reports. See also User Session Limits.