Skip to content
Stand with Ukraine flag

Aliases

An alias is a reference to a single entity or group of entities used as a data source in widgets.

Aliases can be static (pointing to fixed entities) or dynamic (resolved at runtime based on entity type, relations, or dashboard state).

Aliases can be created from the dashboard toolbar or directly while configuring a widget.

From the dashboard toolbar:

  1. Open the dashboard and switch to Edit mode.
  2. Click the Entity aliases icon in the upper-right corner of the toolbar.
  3. In the opened dialog, click Add alias.
  4. Enter the alias name, select a Filter type, fill in the required fields, and click Add.
  5. Click Save in the lower-right corner to apply.

To create a new alias while configuring a widget:

  1. Click the pencil icon on the widget to open its settings.
  2. Go to the Datasource section and select the Entity alias tab.
  3. Type the new alias name and click Create a new one!
  4. Complete the alias configuration and click Add.
  5. Apply and save the widget — the alias is created and assigned immediately.

In the widget settings, open the Datasource section, switch to the Entity alias tab, and select an alias from the drop-down. Add the required data keys and apply.

To edit an alias:

  1. Open the dashboard and switch to Edit mode.
  2. Click the Entity aliases icon in the toolbar.
  3. Click the pencil icon next to the alias you want to change.
  4. Update the configuration and click Save.
  5. Click Save in the lower-right corner to apply.

To delete an alias:

  1. Open the dashboard and switch to Edit mode.
  2. Click the Entity aliases icon in the toolbar.
  3. Click the trash icon next to the alias you want to remove and confirm.
  4. Click Save in the lower-right corner to apply.

The following alias types are available for use in dashboard widgets.

The Resolve as multiple entities toggle (visible in the alias configuration dialog) controls whether the alias can return more than one entity. It is enabled by default for multi-entity alias types (e.g., Entity list, Entity type) and disabled for single-entity types. Widgets that display a single value (e.g., value cards) work with single-entity aliases; table and chart widgets typically use multi-entity aliases.

Alias typeDescription
Single entityResolves to one specific entity chosen by type and name.
Entity listResolves to a manually selected list of entities.
Entity nameResolves to all entities of a given type whose names start with a specified text.
Entity typeResolves to all entities of a specified type, including customers’ entities.
Entity from dashboard stateResolves to an entity passed through dashboard state parameters.
Asset typeResolves to assets of the specified asset profile, optionally filtered by name.
Device typeResolves to devices of the specified device profile, optionally filtered by name.
Entity view typeResolves to entity views of the specified type, optionally filtered by name.
Edge typeResolves to edges of the specified type, optionally filtered by name.
API usage stateResolves to the platform’s API usage statistics.
Relations queryResolves to entities connected via relations to a root entity, up to a specified depth and direction.
Asset search queryResolves to assets of specified profiles connected via relations to a root entity, up to a specified depth and direction.
Device search queryResolves to devices of specified profiles connected via relations to a root entity, up to a specified depth and direction.
Entity view search queryResolves to entity views of specified types connected via relations to a root entity, up to a specified depth and direction.
Edge search queryResolves to edges of specified types connected via relations to a root entity, up to a specified depth and direction.

Resolves to one specific entity chosen by type and name.

Configuration:

Example: An alias filtering one device — Thermometer A1.

Resolves to a manually selected list of entities.

Configuration:

Example: An alias displaying three devices — Thermometer A1, Compressor BC-10, and Compressor QA-32.

Resolves to all entities of a given type whose names start with a specified text.

Configuration:

Example: An alias displaying devices whose names start with “Compressor”.

Resolves to all entities of a specified type, including customers’ entities.

Configuration:

Example: An alias displaying all devices, including customers’ devices.

Resolves to an entity passed through dashboard state parameters. Used in drill-down dashboards to display data for the currently selected entity.

When a user interacts with a widget (for example, clicks a table row), a navigation action can pass the selected entity to the next dashboard state as a named parameter. This alias reads that parameter and resolves to the entity it carries, so widgets in the target state automatically display data for the entity the user selected.

Configuration:

Example: A drill-down dashboard where clicking a device row navigates to a detail state showing data for the selected device.

Resolves to assets of the specified asset profile, optionally filtered by name.

Configuration:

Example: An alias filtering assets with profile “buildings” whose names start with “Build”.

Resolves to devices of the specified device profile, optionally filtered by name.

Configuration:

Example: An alias filtering devices with profile “thermometers” whose names start with “Therm”.

Resolves to entity views of the specified type, optionally filtered by name.

Configuration:

Example: An alias filtering entity views of type “Compressors Entity View Type”.

Resolves to edges of the specified type, optionally filtered by name.

Configuration:

Example: An alias filtering edges of type “edge instance” whose names start with “Edge”.

Resolves to the platform’s API usage statistics.

Configuration:

Example: An alias displaying platform API usage statistics in a widget.

Resolves to entities connected via relations to a root entity, up to a specified depth and in a specified direction.

Configuration:

Example: An alias displaying all assets related to a root entity via a “Contains” relation.

Resolves to assets of specified profiles connected via relations to a root entity, up to a specified depth and direction.

Configuration:

Example: An alias displaying assets of a specified profile related to a root entity.

Resolves to devices of specified profiles connected via relations to a root entity, up to a specified depth and direction.

Configuration:

Example: An alias displaying devices of a specified profile related to a root entity.

Resolves to entity views of specified types connected via relations to a root entity, up to a specified depth and direction.

Configuration:

Example: An alias displaying entity views of a specified type related to a root entity.

Resolves to edges of specified types connected via relations to a root entity, up to a specified depth and direction.

Configuration:

Example: An alias displaying edges of a specified type related to a root entity.