Dictionary fields exist on your table but users can't see them unless they're added to the form layout. This guide shows you how to expose existing fields so all users can view and edit them on every record.
The default form problem
Out of box, ServiceNow tables come with dozens of dictionary fields that aren't visible on forms. When developers add custom fields or when you need to expose system fields like sys_created_by, users can't see them even though the data exists. Admins spend time fielding requests like 'where's the priority field on incidents?' when the real issue is form layout, not permissions or field configuration.
How form layouts work
Every table has a default form view that controls which fields appear for all users. Form Designer lets you drag fields from 'Available' (exists in dictionary, not on form) to 'Selected' (visible to users). This is different from Form Design, which handles sections, columns, and field arrangement within the form. You're working at the field level first — what users can see — then the layout level for how it's organized.
Beyond the default view
Once you understand default form modification, you can create purpose-built views for different teams or workflows. A 'manager_view' might show approval fields that regular users don't need. View rules can automatically show specific views based on user roles or record states. The progression is: get comfortable with default forms, then build targeted views when different user groups need different field sets.
Before you start
- •Form personalization admin or admin role
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Open a record form
Navigate to any record on the table where you need to add fields. You need an actual record open, not the table list view — Form Designer only works from individual record forms.
Use an existing record rather than creating a new one — you'll see current data in the fields you're about to add.
Access Form Designer
Right-click anywhere on the form header (not on a field) and select Configure > Form Layout. This opens Form Designer in a new browser tab with Available fields on the left and Selected fields on the right.
Move fields to Selected
Find the fields you need in the Available list and drag them to the Selected list. Available fields are alphabetical — use the search box if your table has many fields. The Selected list shows current form order from top to bottom.
Double-click a field name in Available to move it quickly instead of dragging.
Position the fields
Drag fields within the Selected list to position them where users expect to find them. Fields appear on the form in the same order as the Selected list. Group related fields together — put priority near state, put contact fields near assignment fields.
Save the layout
Click Save in Form Designer, then close the tab and refresh your original record. The new fields appear immediately for all users on this table. Test with a different record to confirm the fields show up consistently.
Adjust sections if needed
If the new fields landed in awkward sections or need better visual grouping, right-click the form header and select Configure > Form Design. This opens the section and column editor where you can create new sections or move fields between existing ones.
Best practices
Always modify the default view first before creating custom views — most organizations need 80% of fields visible to all users.
Don't add fields just because they exist — each visible field increases cognitive load and form complexity for users.
Test field changes with actual users before rolling out to production — fields that seem obvious to admins often confuse end users.
Document why you added specific fields in the form's annotations — future admins need context for layout decisions.
Group related fields in logical sections rather than dumping new fields at the bottom of the form.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue