Manage Object Relationship

Designer > Objects > {object} > Relationships > {related object}

Relationship Definition

This section displays the cardinality of the relationship. For example, "One to Many".

You can establish a relationship between objects manually by adding a Lookup field. The cardinality of that relationship will then be either one-to-many or many-to-one, depending on which direction you are looking it. That relationship can then be converted to a many-to-many relationship, as described below.

There is also a more fully automated way to establish a many-to-many relationship using the Object creation wizard. Learn more: Junction Object.

To create a a many-to-many relationship

1. Prerequisites:

   • Create the Junction object. (E.g. Orders_Tags)
   • In that object, create a Lookup to the Orders object

2. Select Junction to turn this object into a Junction Object.
   Two additional fields appear.
3. Specify the final destination object and the foreign field (field from the target object) to use as the index. (Typically, that will be the default value--the record ID field.)
4. In the target object's Record Locator, choose the Record Identifier Fields that will be displayed to the user.

How it works

1. The user gets a grid showing the Record Identifier fields.
2. The user examines the list of records, and chooses the one they want for a normal Lookup, or chooses multiple values from the Multi Value Lookup that appears for a many-to-many relationship.
3. The (foreign field) index value for that record is stored in the current record.

Cascade Rules

Your selection here determines which operations on subordinate objects are legal during Composite Object operations.

Learn more: Relationships