- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 02:22 AM
So I have this situation:
- I created a custom table and added it to a workspace.
- I can create new records for this table inside the workspace with a List UI Action "New"
- I cannot open the records from the list page
- When I was investigating the reason why I got this message:
I have looked almost everywhere and I cannot find what I need to change. Can someone help me?
Many thanks in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 06:46 AM
So through my own testing, I found out the issue was the custom application scope that somehow got in the way. I created a new Update Set in a scope provided out of the box and it works fine there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 02:46 AM
can you share the workspace view you created in native form layout?
the view should be in your scope.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 02:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 03:26 AM
that view is in which scope?
Also is it behaving the same for other custom table?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 04:10 AM
I created my own custom scope, and yes I get the same for other custom tables in that scope. The Workspace I am using is also completely custom within that custom scope.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 06:46 AM
So through my own testing, I found out the issue was the custom application scope that somehow got in the way. I created a new Update Set in a scope provided out of the box and it works fine there.