Improved Attribute Filters

This feature improves 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 displays each attribute value even if the secondary label is not unique. This means you 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 is consistent across dashboards, visualizations, and drilling or exploring further interactions, regardless of which label is displayed.

This change is straightforward for end users. However, the metadata have a new ‘Display as label’ parameter 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. The filter is defined by the attribute’s primary label and values, which you should reflect when defining external filters (e.g., in POST messages).

Dashboards using the old attirbute filters don’t need to change. The selection of text from the secondary label is automatically transformed into a selection of individual attribute values with the value of the secondary label.