Null View?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2022 02:19 PM
When I goto to configure form layout i get this message and cloning default view results in an error.
Clearly there is no Null View
Suggestions please

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2022 02:24 PM
Check if there's a view rule on the table, that might be causing this
Aman Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2022 06:58 AM
Hi @Adam Rosenbaum,
Check the view rule 'View' field to contains an empty value of a 'sys_ui_view.name' field.
Take a look at supportive kb - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0750502
Thanks,
Sagar Pagar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2022 02:38 PM
I'm seeing the same issue when impersonating a "citizen developer" (i.e. non-admin; I'm admin and do not see the same issue). I have not figured out yet what to do with any View Rules I can find. The one that I think is causing the trouble was created by glide.maint, so I'm inclined to believe that it's fine and there's something else causing the problem, and possibly an ACL.
Another point to note is that I'm only seeing this on Rome instances (haven't tried S or T). We still have one instance on Quebec where this is not an issue, but it is unfortunately Prod.
For now, my workaround has been to grant admin to the affected user.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2022 01:22 PM
I put in a HI ticket/case about this today and got the following response. Creating the two suggested ACLs corrected the issue.
Most Probable Cause:
There is already a known issue PRB1525799 on Rome version that is documented. Please find the attached PRB.
The issue is fixed in San Diego release.
Solution Proposed:
As a work around please create two new ACLs.
1.Read ACL on sys_ui_view table for role that the effected user has (you can add personalize_role as the effected user has that role)
2.write ACL on sys_ui_view table for role hat the effected user has (you can add personalize_role as the effected user has that role)
Here is the KB for your reference
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1162894