UI builder

[KavanaM77915855]

I am configuring a workspace using UI Builder and have created a page that displays a list of records from a custom table. However, when I click on a record, it doesn't open. Why is this happening, and do I need to configure an event handler for it?

[YashwanthV18760]

Hi @KavanaM77915855 

In Workspace created using UI Builder, list components do not automatically open records like they do in the classic UI. When a user clicks a row in the list, the component only triggers an event. If no event handler is configured, nothing will happen or the workspace may show a “Page not found” message.

To make the record open when a user clicks a row, you need to configure an event handler.

Steps:

1. Open UI Builder and navigate to the workspace page where your list component is placed.

2. Select the List component that displays records from your custom table.

3. In the right-side configuration panel, go to the Events section.

4. Find the Row clicked event.

5. Click Add Event Handler.

6. Choose the action Open Record (recommended) or Navigate.

7. Configure the fields:

   • Table: your custom table name

   • Sys ID: @event.payload.sys_id

8. Save the configuration and publish the page.

After this configuration, whenever a user clicks a record in the list, the workspace will use the Sys ID from the clicked row and open the corresponding record form.

This behavior is expected in UI Builder because navigation between pages or records must be explicitly configured through event handlers.

If this answer helped, please mark it as Helpful or Correct.

[KavanaM77915855]

No it is not working, I tried configuring this before, it will end up with the same issue

[BhavaniYamsani]

Hi @KavanaM77915855 ,

In UI Builder (ServiceNow), a list component does not automatically know what to do when you click a row.
That means:
➡️ Clicking a record will not open a form or details page unless you configure an event handler.
This is expected behavior.

✅ Why a record doesn’t open automatically

• The Data Table, List, or Repeater components in UI Builder only display data.
• Row click (or "Select" event) is just an event — it has no default navigation.
• You must tell UI Builder what action to perform when a row is clicked.

👉 Yes, you do need to configure an event handler.

---

✅ How to Configure Row Click → Open Record in UI Builder

Below are the exact steps.

---

Step 1: Select your List / Data Table component

1. In UI Builder, open your page.
2. Click the component that shows the list of records.
3. Go to the Events tab in the right-side panel.

---

Step 2: Add an Event Handler

1. Click + Add event handler.
2. Choose the event:
   • For Data Table: Row clicked
   • For List: Item clicked
   • For Repeater: Item clicked

---

Step 3: Choose the Action

You usually want one of these actions:

Option A — Navigate to Record (most common)

1. Under Choose an action, select: Navigation → Navigate to URL
2. For the URL, use the record sys_id from the event payload.

Example:

/your_custom_record.do?sys_id={{event.payload.row.sys_id}}

Or for Workspace record view:

/now/workspace/record/<table_name>/{{event.payload.row.sys_id}}

---

Step 4: Map event data to action input

• In the event payload, you’ll often find:
  • event.payload.row.sys_id
  • event.payload.item.sys_id

Map this to the sys_id field in the navigation action.

---

Step 5: Save and Test

1. Save the page.
2. Preview the Workspace.
3. Click a list row → it should now open the record.

Please mark as helpful, if this works for you

Thanks
Yamsani Bhavani

[RakeshM49470519]

Hi @KavanaM77915855 ,

Can you confirm which page you used for this — a custom page or the simple list page template?

If you used a simple list page, you can resolve the issue by using the following approach.

1. Open UI Builder and Select/open your experience.
2. Select Create new page.
3. Select standard record
4. Provide the following details:
   Name : record
   URL path : record
   Type : record 
   Then click Continue and create the page.
   

   
   After creating this page, the issue should be resolved.