Available with Standard or Advanced license.
You can use a wizard to create a composite relationship class. The example in this subtask shows how to create a relationship class between a feature class that stores transformer banks and one that stores transformer units.
The existence of a transformer unit in the database is dependent on the presence of a transformer bank. This relationship class is a composite relationship with the transformer bank as the origin feature class.
The relationship will be nonattributed; composite relationships are by definition one-to-many (1:M) relationships.
Creating a composite relationship involves many of the same steps used in the task for creating a simple relationship. The steps outlined here reflect the differences between the two tasks, including using different origin and destination classes.
- In the Catalog tree, right-click the geodatabase or feature dataset in which you want to create the new relationship class and point to New > Relationship Class.
- Type the name for the new relationship class.
- Click the Origin table or feature class.
- Click the Destination table or feature class.
- Click Next.
- Click Composite relationship.
- Click Next.
- Type the forward and backward path labels.
- Click the message notification direction.
- Click Next.
- Click the second cardinality option. A composite relationship is, by definition, a one-to-many or one-to-one relationship.
- Click Next.
- Click No.
- Click Next.
- Click the drop-down arrow to see a list of fields from the Origin table or feature class. Click the primary key for this feature class or table.
- Click the drop-down arrow to see a list of fields from the Destination table or feature class. Only those fields that are the same type as selected in step 15 are displayed. Click the foreign key that refers to the primary key selected in step 15.
- Click Next.
- Review the options you specified for your new relationship class. If you want to change something, you can go back through the wizard by clicking Back.
- Click Finish to create the new relationship class when satisfied with your options.
The relationship class does not require attributes in this example.
If the relationship class requires attributes, click Yes and skip to Creating an attributed relationship class.