From build 1.5.1610 the data navigator can optionally render references using the values of the key attributes of the referenced object (and the type of the object) instead than just its database id. For example a reference to a folder can be rendered as

    <folderRef objectType="folder">

      <keyVal>/system/users/Guest</keyVal>

      <nav:refObject idref="obj9">

        . . the complete referenced object . .

      </nav:refObject>

    </folderRef>

instead than

    <folderRef idref="obj9">

      <nav:refObject idref="obj9">

        . . the complete referenced object . .

      </nav:refObject> 

    </folderRef>

The syntax used to represent the valus of the key attributes is the same used in the XML accepted by the XML import functions. This means that such XML can be used to transfer objects with references between different system - that can have different numeric ids for objects that are 'the same' = have the same key attributes values.

To enable this rendering for commands that use XML export options - like the 'do.ashx?cmd=feed' command, the 'LoadObjects' workflow activity and the reporting commands - set to "true" the 'RefKeys' XML export options attribute - e.g.:

    <opt:XmlExportOptions 

      xmlns:opt="http://www.teradp.com/schemas/GN4/1/XmlExportOptions.xsd"

      RefKeys="true"

      . . . >

      . . . 

    </opt:XmlExportOptions>

The 'do.ashx?cmd=objsnav' and 'do.ashx?cmd=auditnav' commands - that do not use XML export options - have a new 'RefKeys' URL option - e.g. use:

    .../do.ashx?cmd=objsnav&ids=XXXX&refkeys=

to obtain the XML of the object XXXX with the references rendered as key attributes values.

For the data navigator XML generated internally for attributes automatic computation and editing form initialization, compute and validation use the new 'refKeys' attribute directly in the XML element containing the XSLT definition, e.g.:

    <objectUI>

       . . . 

       <init refKeys="true">

          . . .initialization XSLT . . .

       </init>

       . . . 

    </objectUI>