Difference between revisions of "Common:record fields"

From LongJump Support Wiki
imported>Aeric
 
imported>Aeric
Line 4: Line 4:
<street_address>21 Jump Street</street_address>
<street_address>21 Jump Street</street_address>
</syntaxhighlight>
</syntaxhighlight>
:* In addition to the fields defined in the record, it is also possible to add the [[#Data Policy Bypass Field|Data Policy Bypass Field]] to turn off data policies defined in the platform for this operation.
:* When specifying a [[Multi Object Lookup]] field, you specify the object identifier (name or ID) in the <tt>type</tt> attribute, and the record ID as the field value. The syntax looks like this:
:* When specifying a [[Multi Object Lookup]] field, you specify the object identifier (name or ID) in the <tt>type</tt> attribute, and the record ID as the field value. The syntax looks like this:
::<syntaxhighlight lang="java" enclose="div">
::<syntaxhighlight lang="java" enclose="div">

Revision as of 23:41, 29 June 2011

  • Each <fieldN> element has the name of a field in the object. For example:
<company_name>ABC Co.</first_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>