Advanced Reference Qualifier not working in Portal for Catalog Item

Waleska
Kilo Guru

We have a variable set that asks for a Building location (type of Reference) then we ask users to select a Floor (also type of Reference).

For the Floor variable I did the following in the Advanced Reference Qualifier:
javascript: 'u_building_locationIN' + current.variables.building_location;

This is working on the non-portal view of the Item (so when I was using "Try It") it was working. However, in the portal view (customer view). It is not working. Floor shows "No matches found" consistently.

I did some research and tried the Script Include method, where the script include will have "return 'u_building_locationIN' + building;". Same issue, works when I use the "Try It" option, but doesn't work when testing via the Portal view.

I am guessing it is something simple that I am missing, but all the coffee in the world is not helping me figure this out.

1 ACCEPTED SOLUTION

Turned out to be an issue with the Name calculation script I was using to create the Display name of Floor + Location. All fixed now.

Thank you everyone for the assistance. The fact that it worked on the Try it Now threw me off thinking it was just an issue with the javascript/script include, when the whole time it was an issue with a calculation script of a field within the Floor table.

View solution in original post

23 REPLIES 23

I don't think so. Have you tried:

javascript: 'u_building_locationIN' + current.variables.<variable set name>.building_location;

 

Same result. Works via "Try It", still not working via Portal. I am super stumped.

Just to be sure:

  • Are you sure it is the same item? Can you check the sys_id in the URL?
  • Did you refresh your screen/browser?
  • Try clearing ServiceNow cache by going to yourinstance.service-now.com/cache.do
  • Try in a different browser or incognito mode.

 

Can you also check if there is a Catalog Client script only running on Service portal/Mobile? Or Desktop only? That might effect this behavior?

  • Yes the sys_id is the same
  • Tried clearing cache on browser/instance
  • Checked Catalog Client scripts, there aren't any that should affect this behavior.