- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2023 05:25 AM
Within Configurable Workspace, do List components support Remote Tables?
Here is what I've tried:
1.) When I add my remote table to the List component's 'Table' property, the configuration panel does recognize the remote table's schema since it automatically adds the correct columns to the List component. However, no data records ever appear.
2.) So I tried this next - I created a Data Resource (Global > Look Up Records), and entered my remote table in the Data Resource's 'Table' property. In the data resource's right-hand 'live view' window, I see my external records just fine (in JSON). However, when I hook this data resource up to my List component by setting the 'Table' property to @Data.mydatasource.results, my external records do appear in the List component, but it appears as one long JSON string, and prefaced with: "Exception encountered processing path: /GlideListLayout_Query/getListLayout - Invalid table name"
Am I missing some configuration steps, or are Remote Tables not supported in List components?
Note: As a workaround, I have been able to create a different Data Resource using an EVAM Definition for my Remote Table, and then I use this in a Data Set component instead, using 'List' instead of 'Grid' as the default view.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 12:25 PM
I got this error too and it's related to a missing sys_id (a colleague of mine pointed this out) - the Native UI is able to manage rending without a sys_id but in Workspace, it is required. In my remote table definition, i use gs.generateGUID().toString() to generate a unique ID for each row and this resolved my issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2023 07:26 AM
I can surely say that Remote Tables do work in list component in ServiceNow. I've used them in past.
However, I faced problems where they were not appearing in the table dropdown to select. After clearing cache they appeared.
Also, make sure that the filter is applied on your list component in case the remote table definition is using any variable from the filter.
ServiceNow Community Rising Star 2022/2023
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2023 06:34 PM
Hi, I am having the same issue, were you able to solve it?
My Case replication steps are:
- Open PDI
- Create a remote table (single column is fine)
- Create a definition to populate your table
- Test on UI16
- Open UI Builder and Create a new Experience on a Workspace Shell
- Create a new page & variant with blank template
- Add new List component
- Add the table
- Remove all filters configuration
- Save and Load the page
Error below is displayed on the UI builder & workspace when loaded. I did some other tests that might be valid to tell:
- Create a custom List Layout and tried to apply it
- Create a simple list component instead of a list
- Created a data source using Glide Record Collection Query and a repeater (this one works fine)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2023 08:29 PM
It happens when your remote table has empty rows. Check the table in your remote table and validate that there are no rows with empty data.
ServiceNow Community Rising Star 2022/2023
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 12:25 PM
I got this error too and it's related to a missing sys_id (a colleague of mine pointed this out) - the Native UI is able to manage rending without a sys_id but in Workspace, it is required. In my remote table definition, i use gs.generateGUID().toString() to generate a unique ID for each row and this resolved my issue.