Issue with Data-driven links in new Dashboards: display_id (P-XXXX) vs Internal UUID for Problems

[Fernando_Moreir]

Hi community,

I'm working on a Business Dashboard using DQL and I'm struggling with drill-down links in a table widget. My query fetches events (DAVIS_PROBLEM) and I want to link each row to its specific Problem Details page.

The DQL provides the display_id (e.g, P-26061443), but the new Davis Problems App and event the Classic view seem to require the internal UUID (the long string) in the URL to load correctly. Using pid={{display_id}} often results in a blank page or "Failed to load".

Has anyone found a way to either:

1. Fetch the internal UUID via DQL?
2. Or a URL pattern that successfully accepts the P-ID for a direct drill-down?

I've tried /ui/apps/dynatrace.davis.problems/problem/{{display_id}} and the classic #problems/problemdetails;pid={{display_id}} without success.

Thanks in advance!

[Fernando_Moreir · Accepted solution]

Hi community,

Just an update: with the help of Dynatrace Support, I found the solution for deep linking to the new Davis Problems App from a DQL-based Dashboard.

The Solution:

Instead of using display_id (the P-XXXX format), you must use the event.id field in your DQL query. This field contains the internal UUID required by the Problems App URL.

DQL Snippet:

fetch events | filter event.kind == "DAVIS_PROBLEM" | summarize { ... }, by: { ProblemID = event.id, FriendlyID = display_id }

URL Pattern:

https://{environmentid}.apps.dynatrace.com/ui/apps/dynatrace.davis.problems/problem/{{ProblemID}}

Pro Tip: In the widget settings, you can hide the ProblemID column (UUID) and keep only the FriendlyID (P-XXXX) visible for a cleaner executive look, while the link interaction continues to work in the background.

Hope this helps anyone else modernizing their dashboards!