AgileApps Support Wiki Pre Release

Difference between revisions of "Common:Working with Related Objects"

From AgileApps Support Wiki
imported>Aeric
(Created page with "<noinclude>__NOINDEX__</noinclude> The Related Objects section displays Lookup relationships. In the '''Cases''' object, for example, in the '''Object Relationships''' the r...")
 
imported>Aeric
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
<noinclude>__NOINDEX__</noinclude>
<noinclude>__NOINDEX__</noinclude>
The Related Objects section displays [[Lookup]] relationships.
===Reading the Relationship Grid===
The relationship grid displays objects that are related to the current object by [[Lookup]] fields, and shows how the objects are related:


In the '''Cases''' object, for example, in the '''Object Relationships''' the relationship grid contains lines that look something like this:
In the '''Cases''' object, for example, in the '''Object Relationships''' the relationship grid contains lines that look something like this:
Line 11: Line 12:
:"Many (of the current object) to One (of the object on this line)"
:"Many (of the current object) to One (of the object on this line)"


:''Learn more:'' [[Related Objects]]
The grid columns show:
:{| border="1" cellpadding="5" cellspacing="1"
! align="left"|Column !! align="left"|Content
|-
| '''Relationship&nbsp;Type'''
| Cardinality of the relationship: One to many, many to one, or many to many.
 
|-
| '''Object'''
| The object at the other end of the relationship. Click this link to [[Manage Object Relationship|Manage the Object Relationship]].
 
|-
| '''Alias'''
|The name given to the relationship, for use in [[Composite Object]] operations.
 
|-
| '''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.
|}


====Editing Relationships====
===Editing Relationships===
To change an object relationship, click the name of the related object in the grid.
To change an object relationship, click the name of the related object in the grid.


Line 22: Line 45:
:**A Relationship Alias can only contain alphanumeric characters or the underscore (_) character
:**A Relationship Alias can only contain alphanumeric characters or the underscore (_) character


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

Latest revision as of 19:43, 17 October 2013

Reading the Relationship Grid

The relationship grid displays objects that are related to the current object by Lookup fields, and shows how the objects are related:

In the Cases object, for example, in the Object Relationships the relationship grid contains lines that look something like this:

Relationship Type Object Alias ...
Many to One Accounts

The way to read that line is "Many (Cases) to One (Account)". Or, in general terms:

"Many (of the current object) to One (of the object on this line)"

The grid columns show:

Column Content
Relationship Type Cardinality of the relationship: One to many, many to one, or many to many.
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.
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.

Editing Relationships

To change an object relationship, click the name of the related object in the grid.

Considerations
  • 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.