View Settings icon located in the bottom right corner of the View. There are multiple settings there that controls how visualisation created.
Set title and title font size for View
Show or Hide Legend for Views that have it
Control where legend located. Possible options:
For line and bar charts you enabled or disable dashed lines.
For line and bar charts can select stroke type that used for drawing lines. Possible options:
By default each timeseries field in Y-axis re-use separate axis. If you show 3 timeseries on chart - you will have 3 different Y-axis.
However if measured unit is the same for all fields - you can join them and show on single axis:
Show or Hide X-axis label for View. It cna be usefull for scenarios where Category located on X-axis and label not required.
X axis can be drawn on top of the chart or bottom. This config useful for big heatmaps with scrolls.
When multiple entities are used for visualization and some of them do have telemetry and others don’t it may be useful to remove entities without telemetry from the view (chart/table/heatmap). For making it - enable empty series removing and system will not render them.
Define default sorting for Tables.
Show/Hide Total row for Tables.
Show/Hide export to CSV button for Tables
If chart contains multiple lines/series system applies different colors for them. By select Palette Color, you can define what colors are used.
Note that you can also define specific color for each field individually in field configuration window.
Let’s assume that we have 2 buildings and 2 sensors registered in the ThingsBoard and relations configured among them:
We want to create a view that shows how many sensors are located in each building. In this case results depends on who is the root for calculation - Building or Sensor.
If Building is the root entity - we will see that Building_A has 1 sensor and Building_B has no sensors
If Sensor is the root entity - we will see that Sensor_1 installed in 1 building and Sensor_2 do not installed in buildings
Trendz select Root Entity automatically during view calculation. However you can control what Entity selected as Root for the request:
Trendz create query plan for each view. For making it system collects all fields and entities that are used in the View. Then, using Topology Graph, system identified best query plan for this request by finding the shortest path between used Entities.
For Complex Topology shortest path is not always the best and you modify what entities included in the query plan: