Record fields is not editable

[JuanCarlosE1497]

Hi,

A bit new to ServiceNow but I will try to be concise as possible.

So we created this table and extended it from HCLS case. The table is under our own application scope. We added new fields on this table but since we extended this, there are a lot more existing. The problem now is that after creating the form view and trying to add record for it, the new fields are disabled.

Initial thought was that this is because of scope but if we try other views like HCLS, the fields are editable. Also tried changing scopes while editing the record but didn't do anything. I think, like ChatGPT suggested, that this isn't a scope issue because we can edit the record, just not the newly added fields. ChatGPT, the suggested to look into ACL and scripts but I am also not sure on those since we really didn't add any new scripts to disable or make read-only any or all fields. If there was, then it should affect also the other view. Taking also in consideration that these are only new fields that are disabled. In the screenshot I added, note that the 'Assigned To' is editable because it is an existing field.

I am not sure what else to check right now. Anybody had this issue?

[Ehab Pilloor]

Hi @JuanCarlosE1497,

Only Users with security_admin role can assign the role to other Users. You need to find the security_admin user within platform admins and ask them to assign the role to you.

If no no one has the role, then raise HI case.

Please Accept this response as Solution if it assisted you with your question & Mark this response as Helpful.

Kind Regards,

Ehab Pilloor

[KPNow]

Hi @JuanCarlosE1497 :

Your best bet is to raise a HI case to get this resolved since it appears that nobody has the security_admin role. 

[Tanushree Maiti]

Hi @JuanCarlosE1497 

• Validate write ACLs on the parent table (HCLS case) because security rules can cascade down to inherited or newly added child fields. Create explicit field-level and table-level write ACLs for your custom table if needed.
• Ensure you are working inside your specific application scope
• Check if any active UI policies or client scripts on the parent or child table that have the Inherited flag checked, which might force these fields into a read-only state

•  

[ajmalmuhamm]

Hi @JuanCarlosE1497 ,

If you don't see the New button on the ACL list, it's most likely because you don't have the security_admin role elevated. Although you have the admin role, creating or modifying ACLs requires security_admin.

A few things to check:

• Verify whether security_admin exists in your instance and whether your administrator can grant it to you.

• If the role exists, elevate your role (User menu → Elevate role → security_admin) before navigating to System Security > Access Control (ACL).

• If the role doesn't exist or you can't elevate it, you'll need to contact your instance administrator, as ACL creation is restricted.

Also, before creating new ACLs, use Debug Security Rules while opening the record. This will confirm whether the new fields are being made read-only because of a missing write ACL or another security rule.

Since only the newly added fields are affected while inherited fields remain editable, a missing or restrictive write ACL is a strong possibility.