Record Producer : Reference type and List Collector variable not showing results in service portal

Mukesh Singh
Tera Contributor

Hi Developers,

We have reference and list collector variable in Record producer(Scoped App). Both variable are fetching date from same custom table(scoped app) but for users its showing "no matches found". For admin its working.

We have validated user have read acl for reference table and reference table have Can read, Allow configuration, Accessible for all application access boxes are already checked.

Working fine for user in Native UI but on portal not working for users.

Also when modified field type from reference to Lookup select box, working fine for user on portal as well. 

Please suggest why records are not visible on portal using reference and list collector field for users.

1 ACCEPTED SOLUTION

Not applicable

@Mukesh Singh Read ACL is not enough if your instance in Yokohama ,check for query range ACL as well as being validated.

There is a hack, just impersonate user goto form and type ** you can see value would display.It indicates you have to check query range ACL.

Hope this will help you.

View solution in original post

4 REPLIES 4

Not applicable

@Mukesh Singh Read ACL is not enough if your instance in Yokohama ,check for query range ACL as well as being validated.

There is a hack, just impersonate user goto form and type ** you can see value would display.It indicates you have to check query range ACL.

Hope this will help you.

Mukesh Singh
Tera Contributor

@Community Alums  : Thanks for the update. Yes records are visible when typing ** no fields. What is the solution here. I have also created query_range ACL with the same role as read ACL but records are still not visible for users.

Hi Mukesh,

 

I'm also facing same issue, how did you fix it. 

 

 

fzm
Giga Contributor

This is a common issue with Service Portal. A few things to check:

  1. Field-level ACLs – Even if table ACLs are fine, make sure the display field (like name) has a read ACL for the user.

  2. Table.None ACL – Portal uses this for GlideAjax queries. Make sure it is the TableName.None isn't blocking access.

  3. Cross-scope access – Since it's a scoped app, confirm the reference table is accessible from the portal (global scope).

  4. Reference Qualifier – If scripted, check for any conditions that might fail for non-admins.

  5. Lookup Select Box works because it uses a different data-fetch method, which skips some ACL checks.