Breakdown mapped to the sys_ui_navigator_history table

[crowe1288greg]

I've created a breakdown source using the pa_dashboards table.  I'm trying to create a breakdown mapping relationship with the sys_ui_navigator_history. This table has limited fields. The fields available in this table are: description & URL.

When creating the breakdown source, selecting the 'field', name is not available.

I'd rather not use a bucket group for the breakdown process.   Any suggestions?

[Matthew_13]

Hi Buddy 🙂

 You’re not missing anything here, this is a limitation of sys_ui_navigator_history. That table is very lightweight by design and doesn’t store a direct reference to the dashboard, which is why you’re only seeing description and URL, and not something like name when defining the breakdown source.

Since you’d rather avoid bucket groups (which makes sense), the most practical approach is to derive the relationship yourself. The dashboard information is already embedded in the URL, so the key is to normalize it into something PA can work with.

The cleanest option is to add a small custom reference field (for example, a reference to pa_dashboards) and populate it by parsing the dashboard sys_id from the URL via a simple Business Rule. Once that field exists, you can use it directly in your breakdown mapping and select the dashboard name from pa_dashboards without any hacks.

If adding a field isnt an option, a scripted breakdown mapping is the next best choice — it lets you extract the dashboard ID from the URL at runtime and map it back to the correct dashboard record. It’s a bit more technical, but it avoids schema changes and still keeps you out of bucket groups.

Basically, this is a known data model gap rrather than a mistake on your end, and you’re on the right track. With either a derived reference field or a scripted mapping, you can achieve a clean, maintainable breakdown without resorting to buckets.

@crowe1288greg  - Please mark Accepted Solution and Thumbs Up if you found Helpful 🙂