Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Remote table Record not found

chadlockwood
Kilo Sage

I have created my first remote table and it appears to work as I am seeing the records/data that I expected to see in the list view. However, when I try to open a record, I only see Record not found. I am generating the sys_id in the definition script using:

gs.generateGUID()

and I have added the sys_id column to the list view and validated that I am getting unique values. 

In the System Log, I see 

com.glide.script.RhinoEcmaError: "__ref__" is not defined.
<refname> : Line(1) column(0)
==> 1: __ref__.isNewRecord()

I have tried deleting/recreating the table both in Global and in a scope, and as admin I am not failing the read ACL.

I have looked at other baseline remote tables and am able to open records in form view, so I assume that I have just missed a step.

Has anyone faced this issue and solved it?

 

2 REPLIES 2

hdadmin11
Tera Contributor

I was experiencing this same error as well. However, I was experiencing this error only when I was viewing the list within a Configurable Workspace. If I viewed the list directly ( i.e., by viewing u_st_mytable.list ) and selected a record, it would show in the form just fine.

I was originally using the sample code from the remote table online help: "Example 1: Retrieving all incident records from an external source"

However, after I switched to using "Example 2: Retrieving specific records from a third-party source", it brought up the record appropriately in Configurable Workspace as well. So it seemed that the resolution for me was to implement the "bySysId" function shown in Example 2.

Your issue may not be the same, but it may be something to consider.

Lukas B
Tera Contributor

IDK if helpful but I landed here after I had this issue.

The cause in my case was that I've set a function field as "display". Unfortunately you can configure it this way without any warning message, but the views will crash, also views referencing to such records...