Nest a member under another data type
- Last UpdatedSep 10, 2025
- 2 minute read
UDT nesting is accomplished by creating a member of another data type. You can point a member of one data type to another data type in the Properties pane. Nesting can reduce the time and effort required to create tags. Nesting UDTs up to six levels is supported.
Nest a member under another data type
-
Select the required member that you want to nest.
-
In the Type field of the Properties pane, select the required data type or derived data type under which you want to nest. You can also type the name of the data type in the Type field, to filter the data type.

-
The member is nested under the selected data type or derived data type. You can rename it. For example, rename the nested member "InletValve".
Note: This name is not another instance of a data type. It is another way to reference the data type member of the data type instance.
Example:
“InletValve” is not an actual instance. It does not appear in the root of the tagname dictionary, and it will not appear in the root of a tag hierarchy in the cross-reference utility. You can map the nested member to an instance to reference it in script and animation .
The maximum number of nested UDT levels is six. Consider the following example:
Datatype1.Datatype2.Datatype3.Datatype4.Datatype5.Datatype6.Member1
In this example:
-
"Datatype1.Datatype2.Datatype3.Datatype4.Datatype5.Datatype6" are six levels of the UDT.
-
"Member1” is a basic InTouch tag type such as a memory integer.
Note: Circular referencing is not allowed.
-
Example:
Create a new data type and call it Silo1Type and then add a member called Silo1LevelIndicator.

Now, from the Property Grid, you can change the property Type to be another data type. Say you select LevelIndicatorType.

The nested member is added.
