Difference between revisions of "Common:record fields"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
:* Each <tt><fieldN></tt> element has the name of a field in the object. For example: | :* Each <tt><fieldN></tt> element has the name of a field in the object. For example: | ||
::<syntaxhighlight lang="java" enclose="div"> | ::<syntaxhighlight lang="java" enclose="div"> | ||
<company_name>ABC Co.</ | <company_name>ABC Co.</company_name> | ||
<street_address>21 Jump Street</street_address> | <street_address>21 Jump Street</street_address> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Latest revision as of 21:50, 16 January 2012
- Each <fieldN> element has the name of a field in the object. For example:
<company_name>ABC Co.</company_name> <street_address>21 Jump Street</street_address>
- When specifying a Multi Object Lookup field, you specify the object identifier (name or ID) in the type attribute, and the record ID as the field value. The syntax looks like this:
<field_name type="{objectName}">{record_id}</field>
- For example, in the Sample Order Processing System, if priority tags were in a separate table, then the field might look like this:
<tag type="Priority_Tag">9467890</tag>