User action properties - Conflict when querying similar property key names across applications?

[Inaylor01]

Hi all, 

I'm looking for clarification regarding user action/session properties that have similar key names across applications. 

Say for example:

• I have a custom user action property with a key "loyaltystatus" in application A
• I also have a custom user action property with also with a key "loyaltystatus" in application B
  • The only difference between these two user action properties is their capture expression (as of course, application A and B are different)

Next, a user navigates to both application A and B (which according to the documentation here, it will capture as a single session) and a session is created based on their activity in both applications. 

If I were to search (either by USQL or the User Session UI) for a particular value of property "loyaltystatus" as it relates to Application A, will these searches conflict due to having the same key name? Is it best practice to have either a prefix or a differentiator for certain properties with similar names across applications?

I don't see any sort of restrictions when creating two properties with the same name across applications in Dynatrace, but I wanted to double-check

Thanks in advance

[KiranSomanatti]

Hello,

If the properties are action level, you should not have a problem querying them from USQL, as you can always provide the application name in the WHERE clause.

But the property is session-level, so you would not know from which application it was captured.

As you mentioned about prefixes, you can definitely use the application name as a prefix to easily solve this when configuring the session properties.

Best Regards
Kiran