New/Edit buttons not showing for non-admin users

[Robert Hames]

I have two tables with a many-to-many relationship (Customer & Point of Contact), and have a sys_m2m table related to both of them.

When an admin signs on, the "New" and "Edit" button shows on the table at the bottom of the form. (see screenshot)

When a regular user signs on, the buttons do not appear (see next screenshot). I have roles assigned to the users, and the ACLs for both tables that allow create/edit/delete/read are assigned to those roles.

It appears to me to obviously be a role/rights problem as the true admins can see the buttons and use them.

We recently upgraded from Paris to Rome, and it was working on Paris, but this part was written over a month ago, and is now just being tested by our users, and they found this problem.

Any help/suggestions would be appreciated!

Thanks!

[Allen Andreas]

Hi,

Yea. We both replied about the same thing within a few seconds of each other, haha.

Anyways, so this goes back to ACLs.

Please ensure you look at your "create"/"write" ACL for the table level. Not table.* or table.field_name, but the table level.

Then, see if there's a table.* "create"/"write" ACL as well. The .* can essentially apply an additional scenario that negates the basic table level ACL. So you'd want to check that level too.

If they don't have access there, they can't do 'x'.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Robert Hames]

Below is a screenshot of the create ACL for the Point of Contact table with the roles assigned to it. The user I'm signing in as is part of a group called TSSTaskLead, and below the first screenshot is a screenshot of the group and the roles that are given to a user when they are added to that group.

So, the Link Control doesn't omit the buttons, the ACL has all the roles assigned to it, and the user is part of a group which has at least one of those roles.

I feel like I'm running in circles. 🙂

[Robert Hames]

I also wanted to address if there were any other ACLs for that table. Here is a screenshot of the four ACLs for the table (create/delete/read/write). The create ACL is in a screenshot on my previous reply.

[Allen Andreas]

Hi,

Thanks for providing that. The only other thing I can think of is to checkout this support article and see if the one additional step beyond what you've already looked at, is the issue: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0522170

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Robert Hames]

First of all, thanks for all your help! It turns out it was none of the above. I had a many-to-many table between the two tables, and when you create a many-to-many table in ServiceNow, it doesn't give you the option to automatically create ACLs for that table. So, I didn't think it needed any as it worked when I was signed on as an admin.

Turns out that you have to manually create the ACLs for the sys_m2m table (create/read/delete/update) for all the roles, and then the "New" and "Edit" buttons appear.

Learn something new everyday, and thanks again for staying with me.