Filters
Filters let you limit which entities a widget displays by defining conditions on entity attributes or telemetry keys. Instead of showing all entities from an alias, a widget with a filter shows only those that match your criteria.
Filters are defined at the dashboard level and then assigned to individual widget data sources.
Create a filter
Section titled “Create a filter”- Open the dashboard and switch to Edit mode.
- Click the Filters (funnel) icon in the dashboard toolbar.
- In the Filters dialog, click Add filter.
- Enter a Filter name.
- Click Add key filter to define a condition.
- Configure the key filter (see Key filter settings below).
- Click Add to save the key filter.
- Click Add in the Add filter dialog to save the filter.
- Click Save in the Filters dialog to apply.
The Filter preview at the bottom of the Add filter dialog shows the resulting logical expression in real time.
Key filter settings
Section titled “Key filter settings”Each key filter is defined by three fields at the top:
| Field | Description |
|---|---|
| Key type | Type of entity data to filter on: Time series, Attribute, Entity field, etc. |
| Key name | Name of the telemetry key or attribute (case-sensitive). |
| Value type | Data type of the value: Numeric, String, Boolean, etc. |
Adding operations
Section titled “Adding operations”Inside a key filter, use the Add and Add complex buttons to define conditions:
- Add — adds a simple comparison operation (e.g., greater than 30). Multiple simple operations are joined with AND.
- Add complex — adds a group of sub-conditions joined by either AND or OR. Use this for range queries or union conditions.
Complex conditions can be nested to express patterns like (A AND B) OR (C AND D).
Example — temperature between 10 and 30:
- Operation 1 (Add): greater than
10 - Operation 2 (Add): less than
30 - Both joined with AND automatically.
Example — battery level below 10% or above 95%:
- Add complex, set operator to OR
- Sub-operation 1: less than
10 - Sub-operation 2: greater than
95
Dynamic value
Section titled “Dynamic value”By default, the operation value is a static number or string. You can instead bind it to a runtime attribute by switching the Dynamic source type:
| Option | Description |
|---|---|
| No dynamic value | Use a static hardcoded value (default). |
| Current tenant | Read the threshold from a tenant attribute. |
| Current customer | Read the threshold from the current customer’s attribute. |
| Current user | Read the threshold from the current user’s attribute. |
When a dynamic source is selected, a Source attribute field appears — enter the attribute name to use as the threshold value. This allows different users or customers to see filtered data based on their own attribute values.
Filter predicate user parameters
Section titled “Filter predicate user parameters”Each operation row has an gear icon that opens the Edit filter predicate user parameters dialog. These settings control how the operation value is exposed to dashboard users at runtime:
| Parameter | Description |
|---|---|
| Editable | When enabled, users can change this filter value directly from the dashboard without entering edit mode. |
| Custom label | Custom display label for the filter condition. When disabled, a label is generated automatically (e.g., temperature greater than). |
| Display order | Order in which this predicate appears in the filter panel shown to users. |
| Unit | Opens unit settings: source unit, optional unit conversion, and target units for metric, imperial, and hybrid systems. |
Assign a filter to a widget
Section titled “Assign a filter to a widget”A filter takes effect only when assigned to a widget’s data source:
- Open the widget for editing.
- In the Data tab, find the data source row.
- Click the Filter field and select the desired filter.
- Apply and save changes.
Each widget data source can use only one filter at a time.
Editable flag
Section titled “Editable flag”Each filter in the Filters dialog has an Editable toggle. When enabled, customer users who cannot edit the dashboard can switch the active filter from the dashboard toolbar at runtime. Disable it to lock the filter for all non-editor users.
This is separate from the per-operation Editable setting in Filter predicate user parameters, which controls whether users can change the threshold value of a specific operation.