Problem with action property in USQL

Platform Real User Monitoring
, , , ,
1

Hello,

I am trying to query user action properties using USQL in my Managed environment, but I am not getting any results. Below are the steps I followed:

1. I configured a user action property

image.png
image.png1130×550 18.6 KB

2. I verified that the property is correctly captured and visible within the user action details

image.png
image.png1073×718 34 KB

3. I attempted to query the property using USQL, but the field is not recognized / returns no data

SELECT stringProperties.appointmenttypesummary FROM useraction ORDER BY startTime DESC

image.png
image.png794×647 18.4 KB

I also tried filtering by this property in the User Sessions view, but no results are returned

image.png
image.png400×115 2.97 KB

At this point, I would expect the property to be available for querying and filtering, since it is visible in the user action.
Could you please confirm if there is any additional configuration required for user action properties to be queryable (e.g., indexing, limitations in USQL, etc.)?
Thanks in advance.

2

Hi,
One important point to consider here is the difference between user action properties and user session properties in Dynatrace.

When defining your property, you have the option to store it as:

  • User action property – attached only to a specific action
  • User session property – attached to the entire session

In your case, you’re currently using it as a user action property, which means:

  • it’s only available for specific actions (as seen in the waterfall)
  • in USQL, when querying across many actions, most records won’t have this property → resulting in null

To make it reliably queryable, you can enable:

session.jpg
session.jpg516×163 11.9 KB

“Store as session property”

This way:

  • the value is propagated to the entire user session
  • it becomes consistently available in USQL and filtering
  • it works much better for analysis use cases

Example:

SELECT userSession.stringProperties.appointmenttypesummary
FROM usersession

This approach is generally recommended for business or analytical data like appointment type.