- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2022 11:17 AM
Back story, I have a custom table which I created a few ACLs to grant access to specific groups to be able to read, write and delete to this table. We have decided to allow all users create new records through the application navigator. I tried updating the menu to include the itil role, that didn't help. The form was still read only. I also tried creating an ACL and still the form is read only. Can someone please help me trouble shoot this. I did a impersonation with one of the itil users and turned on the debugger for security. I am only seeing the user does not have create access, but I am unsure how to resolve it.
Solved! Go to Solution.
- Labels:
-
Incident Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2022 05:41 PM
Hi
Thanks.
So you have two create ACLs. One for the entire table (as indicated WITHOUT the .*) and then another specifying all of the fields (indicated with the table.*).
If you've added the itil role to just the ACL that is table.* for create...then that is about the fields...but if they can't create at the table level (again, indicated as table without the .*) then they can't create to the fields if they can't get to the table.
Please double-check your create ACLs, both of them, and ensure they have appropriate access.
Ideally, you wouldn't need the table.* create ACL - delete that and just edit the table create ACL to allow itil. If it's still read only, please check your "write" ACLs as well.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2022 11:25 AM
Hello,
You didn't provide any information as to what type of ACL you created, screenshot, settings, or otherwise.
For this, you mentioned you've given access to read, write, and delete. So, "Create" is left.
Please add a "create" ACL for this custom table and consider adding the role: itil and see if that resolves your issue.
You need to also double-check your "write" ACLs as well...really review ALL ACLs for this table once more to ensure they're properly setup.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2022 11:34 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2022 05:41 PM
Hi
Thanks.
So you have two create ACLs. One for the entire table (as indicated WITHOUT the .*) and then another specifying all of the fields (indicated with the table.*).
If you've added the itil role to just the ACL that is table.* for create...then that is about the fields...but if they can't create at the table level (again, indicated as table without the .*) then they can't create to the fields if they can't get to the table.
Please double-check your create ACLs, both of them, and ensure they have appropriate access.
Ideally, you wouldn't need the table.* create ACL - delete that and just edit the table create ACL to allow itil. If it's still read only, please check your "write" ACLs as well.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!