List Collector in Service Portal

miles9
Tera Guru

Hi all,

I have a custom table that has a reference to the sys_user_group table. I am using a script include and catalog client script.

In the service portal, there is a list collector that points to a custom table. The intended behavior is to pull into the list collector a column of string (UTF-8) but this does not work. Instead I get "No matches found".

Everything, however, works in the platform UI side AND if I am under my admin profile it works fine in the portal.

ONLY under non-admins(including ITIL users) does it NOT work in the Portal side.

I would like to ask for any insight of why this may be the case.

Basically my script include grabs all the groups in the custom table, it grabs all the logged in user's groups they are in, it compares them and if matches are found pushes the matched items into an array.  this is then returned and in my client script I take the matched items and apply a query to the list collector and it produces a list.

 

I'm just looking for any insight as to why it works for everyone on the platform UI and it ONLY works for admins in the portal but NOT for anyone else but this applies to ONLY certain columns.  I have compared the columns and could not find anything that could be the issue.

1 ACCEPTED SOLUTION

Thanks for the suggestions.  

 

I had also created a case with support.  Got an answer.  All the changes with ACL that I never bothered to read up on was the solution.

 

Needed to create a new ACL with the type query_range.  Tested and it works now.

View solution in original post

2 REPLIES 2

GlideFather
Tera Patron

Ahoy @miles9,

 

could you share the codes you wrote? it might be cross-scoped issue, or the non-admins not having the access to the custom table - when you create a custom table it automatically generates basic ACLs (e.g. custom_table.user and custom_table.admin).

 

YOu can either assign the user role to that end user OR deactivate these roles to make it publicly accessible (depends on your desired governance)..

_____
Answers generated by GlideFather. Check for accuracy.

Thanks for the suggestions.  

 

I had also created a case with support.  Got an answer.  All the changes with ACL that I never bothered to read up on was the solution.

 

Needed to create a new ACL with the type query_range.  Tested and it works now.