Why won't my related lists display for non-admin users?

dclayne
Kilo Expert

As an admin, while in the form of a custom application, I selected the Additional --> Configure --> Related Lists option and added the appropriate selection to the form (e.g. the child table has a reference field that obtains its value from the table I'm adding the related list to). This related list displays wonderfully for admins, but not for non-admins.

Here is a screen capture of the form when an admin views it...notice the tabbed region beneath the UI Actions and the hierarchical related lists:

sc01.jpg

Here is a screen capture of the same form and same data when a non-admin views it...notice there are no related lists beneath the UI Actions:

sc02.jpg

When I modify the form design and make the Related Lists part of the Form Layout (e.g. as Embedded Lists), the data displays with the only issue being that it looks ugly:

sc03.jpg

The Related List display issue occurs in domain-separated and non-domain - separated environments. It occurs regardless of the user's domain (e.g. an admin in all the different domains can see the related lists, but a non-admin in any of the domains, including global, cannot.)

So, this leads me to the following questions: are defined Related Lists only available for admins; or, am I missing some table attribute, ACL rule, or system role that would allow my non-admin to see the related lists? I really don't want to use form-embedded lists. Based on the type of data entry that's required, related lists would be much better for the user experience.

1 ACCEPTED SOLUTION

dclayne
Kilo Expert

I figured it out! In table sys_security_acl, there's an out-of-the-box ServiceNow ACL named sys_ui_related_list for read functionality, globally scoped, which makes it so that you must have the admin or form_admin role in order to view related lists within a form. I created a new ACL associated with application, also named sys_ui_related_list, with read functionality, and assigned the application's guest and admin roles to that new application-specific ACL. Now, when I view the forms as a non-admin, I'm able to see the related lists.


View solution in original post

17 REPLIES 17

I found the root cause of my issue, the users didn't have the necessary access to the M2M relationship table involved with the related list. That said, once I corrected it I was able to remove the sys_security_acl that I created earlier and it still works without it. Perhaps that is required for tables in global, whereas I'm only interacting on tables in scope.

Hi Bryan,

how did you fix users access to the M2M relationship table? 

I am having the same issue, and a read ACL had no affect. I am comparing the m2m list to my personal dev instance and they seem to be identical. Any steps you can provide would be appreciated.

Hi Mufeed, sorry for the delay, I just noticed your question. The users needed to have the appropriate access to the actual M2M table, in addition to the task and custom tables for which the M2M table managed relationships. Hope this helps!