About Defining Datasets and Membermaps for Objects with Members
When you apply a dataset to an instance of an object with members, it must link to a membermap that renames and sets datasets for all members of the object instance. A membermap is an imported CSV file. It defines the names of the members and their level in the component. It can also define dataset reference pointers for members in other external datatables.
The first line of a membermap file defines the file type. The second line defines the required membermap parameter field names: Logical name 1, physical name1, dataset1, logical name2, physical name2, dataset2, …
Logical name 1 is the index number of the member in the parent object. Physical name1 assigns a name of your choice to the specified member. Dataset1 is optional and can be used to set datasets for individual members of the group.
Logical name2 is the sequence number of the port on the block, and physical name2 is the corresponding name that you assign. Dataset2 specifies parameter values for the ports themselves. There are two valid data formats for the dataset field:
• The first data format has three values:
◦ The datatable name
◦ The datatable field name that uniquely identifies the row
◦ The specified field value, which identifies a row in the datatable (a dataset)
• The second format is easier to use and has two values:
◦ The datatable name
◦ The datatable dataset $$index$$
When one of the group members is a group (such as a multilevel cable), you must define logical name3, physical name3, dataset3, and so on.
Use the Datatable Explorer to import the datatables and membermaps required before associating a datatable with the group artifact definition.
|
|
Keep the following differences in mind when defining a datatable for a variable group:
|
• There are two indexes in the logical name of a member of a variable group.
• You cannot apply a dataset to a variable group in the catalog, although you can associate the datatable with the catalog item.
