Aliases

An alias is a variable type that points to a source node with a
NodeId
property. Aliases allow you to have instances of an object display different values. For example, by using an alias, an instance of a single motor faceplate can show data for multiple motors dynamically.
NOTE: See Terms dictionary to learn more about aliases.
The alias links to areas of a project information model, making it possible to set up dynamic links so that you can create dynamic logic.
Create an alias in either an object or an object type called a parent node. The source node that the alias points to identifies the source area.
TIP: Create aliases in graphic objects to create a dynamic user interface, such as a widget. The widget may represent a motor type that dynamically shows the values for each different instance of the motor type.

Operation

In object
A
, create an alias that points to the source node
B
. From node
A
or any child node of node
A
, you can create dynamic links to node
B
and any child node of node
B
.
Alias operation

Kind property

An alias contains a Kind property with a value that is a reference node. This reference is to the object or variable type from the source node. When you set the source node of an alias, the Kind property is automatically assigned a value. If the source node is a Motor instance, Kind points to the Motor node.
In a widget where the source node of an alias is set at runtime, you must specify the Kind node. You can create links in the dynamic links browser by using the nodes of the Kind node information model. At design time, these nodes represent the project nodes at runtime.
For example, to design a widget that displays the properties of a Motor type, create a Motor type with two properties -- Speed and Acceleration. Create a MotorPanel type and add the Motor alias. Set the Kind property of the alias to the Motor type node. You can then add two labels or other UI control and dynamically link the Speed and Acceleration properties through the Motor alias.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.