Unable to add the assets to the disposal order via Related List.

[ShivaKumarB9231]

Hello Community,

We are working with a Disposal Order which is in a custom table( part of a custom plugin, not OOTB). Initially, users reported that they were unable to add assets to the "Planned Assets" related list using the Edit option.

Upon investigation, the ServiceNow vendor team confirmed this was due to a known issue (PRB1887019-Users cannot Edit from a Related List on a reference field configured to be read only in the Dictionary (UI16).  ) introduced by a path upgrade. They informed us that this would be resolved in a future patch release.

After applying the latest patch as advised, the issue was partially resolved - however, now only users with admin access are able to add assets using the related list edit option. Previously, this functionality was available to non-admin users as well.

Could someone help us understand why the functionality is now restricted to admin users only after the patch fix, and how we can restore access for the relevant non-admin users?

Thank you in advance for your support!

[Brian Lancaster]

Have you tried using access analyzer? It sounds like there is some soft of ACL issue on the related list if it works for admins and not anybody else.

[wojasso]

Another area to check is the underlying dictionary definition for the table and reference field. When the PRB1887019 patch changed the update behaviour, it also made the related list rely on the dictionary's read‑only flag. If the reference field or the base table is marked read‑only at the dictionary level then non‑admin users will see the "Edit" dialog but will not be able to save a record. This would explain why only admins can add assets after the patch.

Here's what I normally do when I run into this:

• Use Access Analyzer or impersonate a non‑admin user and click the "Edit" on the Planned Assets list. The analyzer will tell you if an ACL is denying update or insert on `alm_disposal_order` or the join table.
• Navigate to System Definition → Dictionary and open the dictionary entry for the reference field linking the asset to the disposal order. Verify that "Read‑only" is not ticked and that it is not a calculated field. If it is read‑only, remove the flag so that non‑admin users can write via the related list.
• Check that there are Create/Write ACLs on the disposal order and asset tables for the roles your users have. After PRB1887019 the platform no longer circumvents missing ACLs; only users with the appropriate ACLs can create records from related lists.

Removing the read‑only flag and adding the correct table/field ACLs resolved the same issue for us.

Let me know if that helps!

[Satish Rana1]

Hi @ShivaKumarB9231 ,

Please try with Acceess analyzer to identify what is restricting users to update it and ensure that no ACL is impacting this.

Check the dictionary entry of the reference field that links assets to the Disposal Order.

Check if it’s set to Read-Only at the dictionary level.

If so, this would prevent non-admins from editing the related list through the Edit option.

Remove the Read-Only checkbox from the dictionary.

Rely on field-level ACLs, UI Policies, or Client Scripts to manage edit permissions instead.

Thank you

[ShivaKumarB9231]

Hi @Satish Rana1 ,

Greetings!

Thank you for your response and suggestion.

I would also like to inform you that this issue was not limited to just "Assets not being added to the Disposal Order", we also experienced similar issue, such as:

1. Stories not being added to Demands via Related list.

2. Demands not being added to Change Requests via Related list.

In all these cases, the reference fields linking these records had the Read-only checkbox set to true at the dictionary level.

As per the ServiceNow vendor team's guidance, after applying the patch upgrade, all these issues have been resolved - even though the Read-only checkbox is still set to true in the dictionary for the fields linking story to Demand and Demand to Change Request. The issues is resolved for admin and non-admin users.

Given this could you please help us understand further whey the issue might still be affecting the Disposal Order case, and what might have changed with the Patch that allowed the other cases to work despite the dictionary read-only setting?

Appreciate your guidance on this!

Thank you.