Assigning Local Names to Template Elements

When a design template is copied, confusion can arise in the identification of members of the template instance. If a template rule refers to an element by its hierarchic position (for example, BOX 1 OF TMPL 1 OF), rule execution errors can arise if the template instance is modified in any way which affects the ordering of the members list. Even if the element has an AVEVA E3D Design name under the Template World, this name will be lost when the template is copied because an element name cannot be used more than once in a Design database.

To avoid these problems, assign a local name (LNAME) to a template member. Each local name, and the reference of the corresponding element, is stored in an array attribute of the template. Local names are therefore set and queried at member element level, even though they are stored at template level. The local name survives a template copy operation.