Error on Agent Workspace

KB15
Giga Guru

Has anyone encountered this error on a list visualization in a workspace? In the UI builder, the list shows up fine.

An error has occurred, variable 'table' has coerced Null value for NonNull type 'String!'

find_real_file.png

1 ACCEPTED SOLUTION

They've created a problem for this. They've told me that this is a temporary workaround. I have not applied this workaround yet.

Set the system property: glide.uxf.js_server.consolidate to false

View solution in original post

10 REPLIES 10

They've created a problem for this. They've told me that this is a temporary workaround. I have not applied this workaround yet.

Set the system property: glide.uxf.js_server.consolidate to false

T_ J_
Tera Contributor

Worked for me - thank you very much!

Good Evening KB -- Fairly new-ish to the platform and I understand about glide records but am more familiar with editing/defining those in script in the advanced view of a form. 

I'm having the same issue you reported.... "Where" did you set the system property to solve the problem you reported.  I'm currently on Orlando Patch 7a--I have not submitted a ticket.  I have looked everywhere and don't know 'where' I'm supposed to look to find the system property to update from true to false (which one, on what object - a page/form/list/table?)  Stumped. 

I meant, good evening TJ... my issue is the same as KBs.

Hi TJ, system properties is accessed by going directly to the table: https://instance_name.service-now.com/sys_properties_list.do. You can also type in sys_properties.list in the Filter navigator field (this is also true for any table).

Most properties are present for the admin to modify but there are properties that don't exist. For this issue, you would simply create a new property

  • Set the name to glide.uxf.js_server.consolidate
  • Set the type to true/false
  • Set the value to false
  • Save the record and test

I recommend doing this in Dev first to confirm.

This fix should have been patched out in October, from last I heard from support, however I have not looked at an updates recently. It's possible it hasn't been patched out.