- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2022 06:39 AM
We changed the ACL for the Contract managers so they can Create/edit the Vendor tables, however they can not add the "Vendor Types" as a selection from the vendor form. The "Vendor Types" table says it's part of the Core_Company ACL but they receive the "Does not have access" window. How do I get them access? Does this reside under another component or would I need to setup a specific ACL for the Vendor Types table?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2022 12:54 PM
The field Vendor Type is referencing the table vendor_type. Your users will need access to this table. I know it's confusing because the right-click and show tells you core_company in a couple of spots. But when you inspect the Reference field value you see the vendor_type table:
The vendor_types table has no ACLs out of the box (or at least in our instance). That means it uses the * ACLs. In our instance we have three for reading records. We are a long time customer, so we do have some old stuff others do not and you may have a different number.
If you have users unable to see the Vendor Type entries, your assumption on the ACL is likely correct (assuming there is data in the table). You can always troubleshooting this theory by creating a read ACL on the vendor_type table (when you do, it should mention it is masking some * ACLs).
When you are debugging ACLs, one great tool is the Field Level Debugger:
https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/contextual-security/concept/c_AccessControlRulesDebug.html
Not sure if you are aware of this, but it can help narrow down the "bad" ACLs that are preventing access. There are other debugging tools, this one is just an easy one in a scenario like this where the user can load the form but is having problems with a field.
Sorry it's a little long winded, I just like to give the background information in case I am misunderstanding the problem. In short, it sounds like you need an ACL on the vendor_type table to allow people to read the records. Just verify you have no ACLs on this table already that you can just use (like a role you created for this). I assume you also need an ACL at some point to allow people to create / write.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2022 12:54 PM
The field Vendor Type is referencing the table vendor_type. Your users will need access to this table. I know it's confusing because the right-click and show tells you core_company in a couple of spots. But when you inspect the Reference field value you see the vendor_type table:
The vendor_types table has no ACLs out of the box (or at least in our instance). That means it uses the * ACLs. In our instance we have three for reading records. We are a long time customer, so we do have some old stuff others do not and you may have a different number.
If you have users unable to see the Vendor Type entries, your assumption on the ACL is likely correct (assuming there is data in the table). You can always troubleshooting this theory by creating a read ACL on the vendor_type table (when you do, it should mention it is masking some * ACLs).
When you are debugging ACLs, one great tool is the Field Level Debugger:
https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/contextual-security/concept/c_AccessControlRulesDebug.html
Not sure if you are aware of this, but it can help narrow down the "bad" ACLs that are preventing access. There are other debugging tools, this one is just an easy one in a scenario like this where the user can load the form but is having problems with a field.
Sorry it's a little long winded, I just like to give the background information in case I am misunderstanding the problem. In short, it sounds like you need an ACL on the vendor_type table to allow people to read the records. Just verify you have no ACLs on this table already that you can just use (like a role you created for this). I assume you also need an ACL at some point to allow people to create / write.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2022 01:15 PM
This is a fantastic response. Thanks for taking the time for the in-depth explanation Trevor. I really do appreciate it.
This will help a great deal!
Mike