About relative and absolute bindings

Data bindings, like ORDs, can be relative or absolute.

Since ORDs can be relative or absolute and widgets are bound to data sources using an ORD, data bindings can be relative or absolute, as shown here.

This is a particularly important point to remember if you want to design Px files that are used in multiple views on a local station or even possibly for use across different stations. When you use the Px Editor tools to bind data, the ORD is usually supplied in an absolute format, by default. The ORD is relative to the station, such as:

station:|slot:/Logic/HousingUnit/AirHandler/DamperPosition

This absolute path ensures that the data always resolves to a single unique component (DamperPosition) in the location that is specified by the ORD, regardless of where the Px file or the parent component is located. If the same Px file is attached to a view that belongs to a different component, the ORD will still resolve to the original DamperPosition component because of the absolute path. However, if you make data binding relative, then the path will resolve relative to its current parent ORD. This relative path makes the Px file resolve data bindings correctly to identically named components that reside in different locations, thus making one Px file usable in many views.

You can open the Relativize ORDs window from the Bound ORDs palette, as shown. This Px Editor tool provides a convenient way to change absolute ORDs to relative ORDs.