I need to hide custom fields in list view and from view for all cmdb_ci and cmdb_ci child tables

[RajeshPavaK]

Hi,

i have custom fields (u_source,u_ci_owner_responsible,etc....) now i need to hide this fields in form view,list view,workspace view for all cmdb_ci tables and cmdb_ci child tables

[AJ-TechTrek]

Hi @RajeshPavaK ,

As per my experience, below are steps which will be helpful for you.

1. Form View (Standard UI)

You can hide fields for all CMDB classes by removing them from the default form layout:
Steps:
1. Go to System UI → Form Layout.
2. Table: cmdb_ci (the base class).
3. Move u_source, u_ci_owner_responsible, etc. to the Available list (remove from form).
4. Save — all child tables that inherit from cmdb_ci will also lose the field on their form unless they have overridden layouts.
5. If child tables have their own form layouts, repeat for those tables.

Tip:
If you want to keep the fields in the database but not visible to anyone, you can also control via Dictionary Attribute → Read roles.

2. List View (Standard UI)

To hide fields in all list views:
Option A – Remove from Default View
1. Open any cmdb_ci list.
2. Right-click the column header → Configure → List Layout.
3. Remove those fields from the Selected list.
4. Save — cascades to all child tables unless they have overridden list layouts.

Option B – UI Policy to Hide in Lists (Not Recommended for Performance)
You could technically do this with client scripts, but removing from list layout is cleaner.

3. Workspace View (CMDB Workspace / Agent Workspace)

Workspace forms and lists are managed through UI Builder.
Steps:
1. Go to UI Builder.
2. Open CMDB Workspace → Find the page for your CI form (e.g., cmdb_ci Record Page).
3. Locate the Form component.
4. Remove those fields from the field set in the form configuration.
5. Repeat for any list/grid components in workspace where these fields appear.

Tip:
If your workspace uses a Form View Configuration (via Form Designer), removing the fields from that config will hide them everywhere.

4. Role-Based Restriction (Optional & More Secure)
If you truly never want these fields visible:
1. Go to System Definition → Dictionary.
2. Search for u_source and u_ci_owner_responsible.
3. Set Read roles = admin (or empty to block all unless role is given).
4. This will hide in:
* Forms
* Lists
* Reports
* API responses
* Workspace
This is the most secure option because it applies at the ACL/data level.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025

[Ankur Bawiskar]

@RajeshPavaK 

where are those fields created?

On child tables or parent table i.e. cmdb_ci?

if you want to hide then why not deactivate those?

best way to hide -> Create field level READ ACL and set answer=false in advanced script

This will hide it from form, list etc

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Dr Atul G- LNG]

Hi @RajeshPavaK 

https://www.servicenow.com/community/developer-forum/hide-a-field-in-child-table-from-extended-paren...

As you want to hid from every  where to best is ACL 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0719142