Upcoming Change: Improved Attribute Filters We are updating how attribute filters handle values with non-unique secondary labels, such as users sharing the same User Name. Current Behavior: When an attribute (e.g., User) has a unique primary label (e.g., User ID: 1234) and a more readable secondary label (e.g., User Name: John Doe), filtering by the User Name (if multiple users are named John Doe) results in all John Does being combined into a single filter value. New Behavior: The improved filter will display each attribute value even if the secondary label is not unique. This means you will see all instances of John Doe separately, with a tooltip showing the primary label (e.g., User ID) to help differentiate them. The filter's behavior will be consistent across dashboards, visualizations, and drilling or exploring further interactions, regardless of which label is displayed. This change is straightforward for end users. However, there will be a new 'Display as' parameter in the metadata to indicate which label should represent the attribute in the GUI. This parameter must be considered when using filters in dashboards, visualizations, drilling, POST messages and events, SDK filter definitions, and cross-filtering. More details will be provided in upcoming release notes.

Does this mean we will need to change our current dashboards to align?

We do not expect change of existing dashboards will be needed. Selection of text of secondary label will be automatically transformed into selection of individual attribute values with the value of the secondary label.

Ok, hopefully