Difference between revisions of "Related Objects"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 46: Line 46:
:* [[Object Relationships]]
:* [[Object Relationships]]
:* [[Composite Object]]s
:* [[Composite Object]]s
==Working with Relationships==


===Editing the Relationship Information Grid===
===Editing the Relationship Information Grid===

Revision as of 23:09, 30 September 2013

GearIcon.png > Customization > Objects > {object} > Object Relationships > Related Objects

About Related Objects

A Related Object is a participant in an Object Relationship.

If the record you are viewing is the target of a Lookup, then one or more records in another object could be pointing to it. The other object in that case is known as a Related Object, that contains Related Records. (When viewing data, those records are displayed in the Related Information section of the record you are viewing.)

For example, in the Sample Order Processing System, records in the OrderItems object "look up" to records in the Orders object. When viewing an Order record, those records appear in the Related Information section. When entering an Order, the Form may display them in a Subform (a table of related records).

So:

From the standpoint of the Orders record:
  • There can be multiple related records in the OrderItems object.
  • When you view an Order, the related records appear in the Related Information section of the Order form.

Learn more:

The Relationship Grid

This grid displays objects that are related to the current object, and how they are related:

Column Content
Object The object at the other end of the relationship. Click this link to Manage the Object Relationship.
Alias The name given to the relationship, for use in Composite Object operations.
Relationship Type Cardinality of the relationship: One to many, many to one, or many to many.
Junction To If the relationship is many to many, then the object is a Junction Object. This column gives a link to the object on the other side of the junction.
Cascade Rules In this section, you establish the Cascade Rules that govern Composite Object operations.

Learn more:

Editing the Relationship Information Grid

  • Any relationship can be managed by clicking on the object link in Relationship Information grid
  • For Many to One relationship, only Alias and Update Cascade Rule is available to update
  • Relationship Alias is a required field and it should be unique for a given base object
    • Alias cannot be "Users" or "User"
    • A Relationship Alias can only contain alphanumeric characters or the underscore (_) character

Deleting Relationships

Relationships are formed by Lookup fields. To delete a relationship, delete the lookup field that created it.