How to use Catalog Item variables in Platform Analytics dashboard interactive filters?

ClaymoreH
Tera Contributor

Hi everyone!

I'm working on a dashboard in Platform Analytics using the sc_req_item table, and I need to create an interactive filter based on a Catalog Item variable. When creating a Single Select filter in Platform Analytics, the field selector doesn't allow me to select Catalog Item variables directly.

I tried using sc_item_option, sc_item_option_mtom, and question_choice as filter sources, but couldn't get the filter to apply the variable condition correctly to the RITM visualizations.

I found a workaround by manually editing the filter's JSON configuration, setting the variable path in both datasource and targets:

"datasource": {
  "type": "table",
  "payload": {
    "field": "variables.67ef6f7e93ec1b100c9975dcebba1026",
    "table": "sc_req_item",
    "primaryKey": "sys_id"
  }
},
"targets": [
  {
    "type": "table",
    "payload": {
      "field": "variables.67ef6f7e93ec1b100c9975dcebba1026",
      "table": "sc_req_item",
      "primaryKey": "sys_id"
    }
  }
]

After making this change, the Platform Analytics editor recognizes the field as Requested Item → Department, which is exactly what I wanted.

Captura de tela 2026-11-18 120449.png

 

Captura de tela 2026-11-18 120640.png

 

Captura de tela 2026-11-18 120745.png


However, manually modifying the JSON feels like a workaround rather than a supported configuration.

Is there a native way to select Catalog Item variables as the source and target of an interactive filter in PA?

Thanks!

1 REPLY 1

HasanM
Kilo Sage

Hi @ClaymoreH 

As far as I'm aware, interactive filters in Platform Analytics don't support catalog item variables natively. Your JSON edit works, but it's unsupported and may break on upgrade or when someone edits the filter in the designer.

The cleaner approach is to add a field to sc_req_item (for example u_department) and populate it from the variable with a flow or a before-insert business rule. Backfill existing RITMs with a fix script. You can then use the field natively in filters, breakdowns and indicators.

An alternative is a database view joining sc_req_item with the variable tables, but it's slower and reference variables return sys_ids.

If this helped, please mark it as the accepted solution.