ACL issue on new table

[rachelconstanti]

I created a custom table.

One of these fields is a reference field on a catalog item.

When a non-admin tries to submit the form, the reference field shows 'no matches found'.

I have created a read ACL and added the itil role, but the result is the same - 'no matches found'

This is only happening via the Service Portal.

If I access the catalog item via the User Interface as an itil user, the values are displayed and selectable.

What am I missing?

@Ankur Bawiskar - any help you can offer is appreciated.

Thank you,

Rachel

[yashkamde · Accepted solution]

Hello @rachelconstanti ,

This sounds like an ACL issue as that table is possibly only allowed to be "read" by ITIL.

Please navigate to your ACL's and look for this table and all "read" ACLs and see if you need to add/create one without any roles specified (so that everyone can read)...or tweak one that's already created.

System Security > Access Control (ACL)


If my response helped mark as helpful and accept the solution

[Ankur Bawiskar · Accepted solution]

@rachelconstanti 

The response marked as correct I believe is not related to your query

you need to create query_range ACL with Table.* 

Give role to that ACL and it will start showing records for non-admins in portal reference variable

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar · Accepted solution]

@rachelconstanti 

The response marked as correct I believe is not related to your query

you need to create query_range ACL with Table.* 

Give role to that ACL and it will start showing records for non-admins in portal reference variable

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar · Accepted solution]

@rachelconstanti 

any update to this?

[rachelconstanti]

@Ankur Bawiskar 

Just seeing this now

Creating the query range ACL did indeed resolve the issue.  

Again - THANK YOU for the support