- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2024 07:37 AM
Hello,
In change request form, I'm not able to view the 'edit' button in 'Incidents Caused By Change' related list. Though the 'Omit edit' checkbox is unchecked in list control of this related list, the edit button is not visible and when the change request is closed, 'new' button of this related list is also disappeared. Screenshot of the related list is attached below.
Thanks
Pavithra
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2024 07:53 AM
Hi there,
Out-of-the-box, on for example "Incident Fixed by Change" there is Edit + New, while on "Incident Caused by Change" there's only New. This has nothing to do with List Control and Omit Edit. This has to do with "Reference Floats" which is configured on the Dictionary Entry of the Reference field.
For example, on Incident field "Change Request":
On Incident field "Caused by Change":
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2024 07:41 AM
I would check the UI action on the table the related list is referencing and ensure the conditions are being met to have the button show up.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2024 07:53 AM
Hi there,
Out-of-the-box, on for example "Incident Fixed by Change" there is Edit + New, while on "Incident Caused by Change" there's only New. This has nothing to do with List Control and Omit Edit. This has to do with "Reference Floats" which is configured on the Dictionary Entry of the Reference field.
For example, on Incident field "Change Request":
On Incident field "Caused by Change":
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 02:11 AM - edited 07-15-2024 02:18 AM
Hi Mark,
Yes in incident table I got a field named 'cause by change' and its 'reference floats' is unchecked in dictionary level.
Thanks
Pavithra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2025 06:09 AM
Hello Mark,
I have a similar requirement, but it pertains to changes. Currently, users are unable to add CIs to a change once it is no longer in the "New" state. I would like users to add CI's to change unless it is closed and to allow admins to add CIs to a change even after it has been closed.
To address this, I have attempted the following:
- Enabled "Reference Floats" for the task, but this did not work.
- I can see the edit button, but it does not save the CIs.
- Modified the create ACL script on the form to allow adding CIs, but this also did not work.
Would you be able to provide any suggestions or guidance?
Thank you,
Hari