Right click menu is not working on some records

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 06:15 AM - edited 05-25-2023 06:17 AM
Recently we discovered that some of our computer records do not allow the right-click context menu. We use this quite a bit to save and reload forms, as I am sure many do. It's a random issue it appears.
What I would expect
What we are finding in some records
Our computer records are not touched frequently. We only found this as the computer was End Of Life, and when editing the records encounter this. It does not appear to be happening in Incidents, problems, or Change records.
On the record where the menu is not working, I do see this when in Dev tools for the browser.
I do not see this appear on the records where the menu works. I am not understanding the error or where I might look.
Any help is appreciated and I have searched the article for the same issue, though I am not able to find or resolve with the information I have found.
- Labels:
-
Service Desk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 06:20 AM
this happens when your form is broken.
Check browser console errors
Some client script, ui policy is causing that error
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 07:58 AM
So the last image does show a UI Policy though not sure on what that is or how to pull that info out. Why is not affecting all records

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 08:07 AM
One thing to add. If I delete the computer record that has an issue with the context menus. Create a new record for it, then it works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2024 12:38 AM
Had the same error, it was a UI Policy that was incorrectly set up.