Can we disable a field on child table ?

[gazalagrawa]

I see NEeds attention and action status field on task table, and they are visible on sn_customerservice_case personalise list fields too. How can I disable these fields not to be visible anywhere on case table?

[Sachin_Nasa]

Hi gazalagrawa,
Yes, those fields are coming from the parent table.

In this case, Case (sn_customerservice_case) extends Task, so fields such as Needs attention and Action status are inherited from the Task table. Because they are parent fields, you cannot disable them only at the child table level by deactivating the dictionary entry — that would impact all tables that extend Task.

If you want them not to appear on the Case table, you have a few options:

🔹 Hide at the form/list level (recommended)
Remove the fields from the Case form layout
Remove them from the Case list layout / personalize list
Configure views so they are not shown to users

🔹 Use Dictionary Overrides (best practice for child-specific behavior)
Create a Dictionary Override on sn_customerservice_case for those fields and:
Set Display = false or Read-only
Adjust attributes such as mandatory/visibility only for the Case table
This keeps the fields available on Task but hidden for Case.

🔹 Use UI Policies / Client Scripts
If visibility needs to be dynamic, you can hide the fields using a UI Policy on the Case table.

Hope this helps!
If this resolves your issue, please mark the response as Helpful and accept it as the Solution so it can assist others as well.

[Tanushree Maiti]

Hi @gazalagrawa 

You can  not do it. It will impact parent field in Task table.

Go through this community post: it will help you.

https://www.servicenow.com/community/in-other-news/avoid-issues-when-modifying-shared-fields-in-exte...

[Sandesh Powar]

Hello @gazalagrawa 

1. Do Not Delete the Fields
“Needs attention” and “Action status” are system fields inherited from the Task table and used by CSM logic. Deleting or deactivating them can break workflows, SLAs, or workspace components.

2. Remove from Form View
Open a Case record → Right-click header → Configure → Form Layout → move both fields to the left (remove from form) → Save.

3. Remove from List View
Open the Case list → Right-click any column header → Configure → List Layout → remove both fields → Save.

4. Prevent Users from Adding via Personalize List
Go to System Definition → Dictionary, search for those fields, open each record, and add the attribute no_list (and optionally no_form). This prevents them from appearing in list personalization.

If my response helped resolve your query, please mark it as Correct ✅ and close the thread 🔒 so it can help other community members find the solution more easily.

Regards,
Sandesh Powar