User Manual

Graphics Builder
Overview
5
A6V11604297_en--_g
67 | 195
Fig. 7: Modifying the GRAPHIC ON.
Creating Root level graphics
This topic outlines tips for creating a graphic that displays data from multiple sites or data for an entire project.
● When using TOOLS > RELATIVIZE to generate bindings, the root of the search pattern is always the $id
variable.
● The binding query is always relative to the structured object in the Plant view where the graphic is
opened for viewing or editing.
– The $id variable in each relative binding query dynamically assumes the value of the site (for example, a
building) or equip (for example, an AHU plant) where the graphic is opened for viewing or editing.
– The $id variable cannot assume the value of topLevel, which is the tag that identifies the Root level
in the Plant view.
– There is not a “topLevelRef” that behaves like siteRef or equipRef to describe the parent/child structure
in a binding query.
● The binding query can be manually altered in advanced cases, such as where the binding always starts
from the same structured object. For example, a specifically named site under the Root level.
● Use > > Export files and Import files to reuse a Root level graphic on another system device that
has the same building hierarchy and uses the same naming convention.
● The $id can be manually removed and replaced with a specific navName.
– Binding defined by navName instead of the $id variable is not affected by where the graphic is opened
for viewing.
– GRAPHIC ON can then be set to any place in the project structure where it is convenient for this graphic
to appear, including the special topLevel tag that identifies the Root level.