Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Add a drilldown event to a data visualization on a technical dashboard

Technical dashboards do not support preconfigured destinations for drilling down from a data visualization. If you want a viewer to open a more detailed view of the data when they interact with a visualization, configure a custom drilldown event.

Before you begin

This procedure assumes that you have already created a technical dashboard and populated it with a data visualization component.

Warning: This procedure does not apply to Saved Visualization components.

Role required: ui_builder_admin, rights to edit a technical dashboard

Procedure

  1. Navigate to All > Platform Analytics > Library > Dashboards.

  2. Locate and open the desired technical dashboard.

  3. Select Edit in UI Builder.

  4. In the UI Builder, select the desired data visualization in the dashboard.

  5. In the configuration panel for the data visualization, open the Events tab.

  6. If your only option is to add an event mapping, do so.

Image omitted: add-event-mapping.png
Making a data visualization component interactive.
1.  Select **Add event mapping**.

2.  In the list of events, select **Visualization Clicked**.
Image omitted: visualization-clicked.png
Selecting the Visualization Clicked event.
3.  Select **Continue**.
  1. If the Visualization Clicked event is already listed on the Events tab, select Add handler for it.
Image omitted: techdash-add-handler.png
Adding a handler to the Visualization Clicked event.
  1. Search for and select the Advanced dashboards - Redirect event handler and Continue.
Image omitted: db-adv-db-redirect.png
Selecting the Advanced dashboards - Redirect event handler.
  1. Configure the event handler as follows.

    FieldJSON typesDescription
    Contextobject, with a string property named pathThe path of the experience where the destination page resides.
    RoutenoneThe route name of the destination page.
    Route fieldsobject, with all parameters as stringsRequired parameters for the destination page.
    Optional parameters Optional parameters for the destination page.

    The required and optional parameters for common targets follows:

    TargetRoute fields (required parameters)Optional parameters
    List{table:@payload.params.table}{query:@payload.params.query}
    Record{table: @payload.params.table, sysId: @payload.parms.row.sys_id.value}None
    KPI Details{uuid:@payload.params.indicatorSysid}None
  2. Select Add.

Drilldown for a table data source

You have a vertical data visualization that shows the number of records on the Incident [incident] table grouped by Priority. When a viewer interacts with this visualization, you want it to open a list of Incident records in the Platform Analytics experience.

Note: This example uses the Context of the Platform Analytics experience and default Route names to components therein.

  1. You follow Steps 1-8 in the general procedure, so you now have the configuration open for the Advanced dashboards - Redirect event handler for your vertical bar visualization.
  2. In the Context field, you select Edit.
Image omitted: db-adv-db-ex-edit-context.png
The Edit control in the Context field.
  1. In the editing dialog, you select the object JSON type.
Image omitted: db-adv-db-ex-json-object.png
Selecting the object JSON type for the Context.
  1. You select Add property and enter path as the property name and now/platform-analytics-workspace as the property value. These values specify that the viewer drills down to the Platform Analytics experience.
Image omitted: db-adv-db-ex-context-value-table.png
Setting the value of the Context.
  1. You select Apply and move on to the next field.
  2. In the Route field, you enter simplelist. This route leads to the simplelist page in the Platform Analytics experience.
  3. For the Route fields, you first choose to bind data.
Image omitted: bind-data.png
Selecting to bind data.
  1. Then you add the property {table: @payload.params.table} to the field. This property passes the name of the table in your visualization to the simplelist page of the Platform Analytics experience.
    1. You select the Event payload property params and then table.
Image omitted: db-tech-adv-redirect-table-param.png
Selecting the payload.params.table property in the data binding editor.
2.  You double-click, drag and drop, or select the arrow to add the property to the upper area of the editor.
3.  Double-click on the property in the upper area of the editor to open it for editing.
Image omitted: db-adv-event-edit-prop.gif
Double-clicking the property pill to open it for editing.
4.  You surround the `@payload.params.table` property with curly brackets and add the `table:` property.
Image omitted: db-tech-event-complete-parm.gif
Completing the table property.
5.  You select **Apply**.
  1. Similarly, you choose to bind data for the Optional parameters field and set the value {query:@payload.params.concatenatedQuery}.

The properties of your Advanced dashboards - Redirect event handler now appear as follows:

FieldValue
Context{path:now/platform-analytics-workspace}
Routesimplelist
Route fields{table:@payload.params.table}
Optional parameters{query:@payload.params.query}

In runtime, a user can interact with the visualization to open a list of Incident records.

Image omitted: db-adv-ex-ddown-table.gif
Opening a list of Incident records by clicking a Single Score visualization on a technical dashboard.

Drilldown for an indicator data source

You have a Line data visualization for the indicator Number of open incidents. When a viewer interacts with this visualization, you want it to open the KPI Details page for that indicator.

  1. You repeat steps 1-5 from the Table data source example, because in this case too you are drilling down to a page on the Platform Analytics experience.
  2. For the Route, you enter ac_kpi_details.
  3. For the Route fields, you first choose to bind data
Image omitted: bind-data.png
Selecting to bind data.. Then you enter `{uuid: @payload.params.indicatorSysid}`. This parameter passes the id of the indicator, in this case Number of open incidents, to the Platform Analytics experience KPI Details page.
**Tip:** First use autocomplete to add the data parameter `@payload.params.indicatorSysid`, then surround that parameter with curly brackets and add `uuid:`.

The properties of your Advanced dashboards - Redirect event handler now appear as follows:

|Field|Value|
|-----|-----|
|Context|\{"path":"now/platform-analytics-workspace"\}|
|Route|ac\_kpi\_details|
|Route fields|\{uuid:@payload.params.indicatorSysid\}|
  1. No other parameters are necessary, so you select Add and then Save the UI Builder page.

In runtime, a viewer can interact with the visualization to open KPI Details for the Number of open incidents indicator.

Image omitted: db-adv-ex-ddown-indicator.gif
Opening KPI Details by clicking a Line visualization on a technical dashboard.

Parent Topic:Technical dashboards

Related topics

More examples and information are available in KB2663434