Hi y’all, Carolina from support here!!
I’d like to share a tip to simplify dashboards and improve performance: use a single interactive Table widget that filters data based on the user’s selection (device, group/segment, and time range), instead of maintaining multiple static tables.
How it works:
-
Device switching with Blueprint: Configure your dashboard as a Blueprint and add a Blueprint Device (or Entity) using tags. This gives you a device selector at the top of the dashboard so users can switch the active data source on the fly. The Table widget’s “Data From” should reference the Blueprint device and the relevant variables. According to the Blueprint Devices and Dashboards documentation, the blueprint selector is driven by tag key/value and lets the same widget configuration work across many devices/entities without duplication.
-
Time filtering in the widget: Use the widget’s built-in date filters (minutes, hours, days, weeks, months, or custom) so users can quickly change the time range for the same table, avoiding separate tables per range. Line chart widget and Area chart widget docs illustrate these filter controls, which also apply to time-based data.
Other implementation tip: build your dashboard as a Blueprint, tag your devices/entities properly, and select the Blueprint device as the Table’s source.
With this setup, your users interact with one Table that updates as they switch devices (via Blueprint), choose groups/segments (through variable design and widget configuration), and apply time ranges (via built-in filters or metadata). A single table that adapts to user selection reduces the number of widgets, which helps stay within dashboard limits and lowers front-end load (:
Was this tip helpful to you? I hope it can be useful to ours users (:
Happy weekend,