Difference between revisions of "Referential Field"
imported>Aeric |
imported>Aeric |
||
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
For example: | For example: | ||
:{| | :{| | ||
<tt>customer.email</tt> | | <tt>customer.email</tt> | ||
|} | |} | ||
| Line 16: | Line 16: | ||
It is also possible to ''chain'' the Lookup references, like this: | It is also possible to ''chain'' the Lookup references, like this: | ||
:{| | :{| | ||
<tt>customer.state.tax_rate</tt> | | <tt>customer.state.tax_rate</tt> | ||
|} | |} | ||
| Line 28: | Line 28: | ||
:* Referential fields are available for use in these contexts: | :* Referential fields are available for use in these contexts: | ||
::* [[Formula Fields]] | ::* [[Formula Fields]] | ||
::* [[Validations]] | ::* [[Validations]] | ||
Latest revision as of 00:44, 12 January 2013
A referential field is a reference to a field in a related object. For example, in the Sample Order Processing System, the Order object has a customer field that "looks up to" to the Customer object.
Because of that Lookup relationship, the customer field can be used to reference a field in the associated Customer record, using dot notation. For example:
customer.email
Here, the customer field in the current Order record points to the target Customer record, and the value of the email field in that record is used.
It is also possible to chain the Lookup references, like this:
customer.state.tax_rate
In this example, the state field in the customer object looks up to a hypothetical tax table, where tax rates are stored. Things are never that simple, of course, but the example shows references can be chained, so long as the Lookup relationships exist.
- Considerations
-
- Referential fields can chain to arbitrary depth.
- Referential fields are available for use in these contexts: