Does anyone know if it's possible to expose a reference field variable on a public Service Portal page?

Angelo Surian · ‎07-09-2020

Hi everyone! Been pouring over community content and can't seem to find the answer to this. Before I go any further, does anyone know if it's possible to expose a reference field variable to unauthenticated users on a public Service Portal page?

Any guidance/solution would be appreciated. Thx.

Angelo Surian · ‎07-13-2020

Ok so this thorn in my side has finally been removed. I hope that this helps others looking for a similar solution. Please mark as Helpful if it does.

Here are the requirements for exposing a service portal page with a record producer/catalog item with reference variables to unauthenticated users:

1) All Service Portal pages for the SP Portal you wish to expose must be set to Public = true

2) Any widgets that are part of this portal must be set to Public = true

3) The record producer / catalog item must have the "public" role added to Roles

4) All variables that are part of the record producer/catalog item must have "public" added to Read roles, Create roles, and Write roles permissions.

5) And for the most important one, if you wish to expose reference field variables, you will need to add a processor execute ACL called "SPListDataProcessor" There is already an OOB ACL for this that SP leverages but you can leave that one alone. Just add a new one with no required roles and nothing in the script field like this.

View solution in original post

Abinash · ‎03-23-2021

Hi Angelo,

I do have a same requiremnt where i have a refernce field exposed on a catalog item and that variable is referring to a custom table. I tried to replicate the same ACL as mentioned by you but still no luck. All the variables and catalog item are visible for the unauthinticated users. Can you let me know if i am missing something. I even tried to inactive the oob acl and check still no result.

Any inputs from you will help me out

Angelo Surian · ‎03-25-2021

Hi Abinash. To confirm, you've added Public to the reference variable Read, Create and Write role permissions? Other than that, are there any special ACLs on the custom table itself that could be restricting access?

Abinash · ‎03-25-2021

Hi Angelo,

Yes i have provided all the operation roles to that varibale but still no luck. Did you do any extra steps of customization to achieve this

Angelo Surian · ‎03-25-2021

Just the exact steps I outlined. I'll see if I can replicate what you're experiencing on my side.

Angelo Surian · ‎03-25-2021

Curious Abinash, have you upgraded your instance recently? I ask because the upgrade will overwrite a customized SPListDataProcessor acl and replace it with OOB which will definitely prevent public users from seeing any reference field variables.