Combining the two: binary files with custom fields

It is possible to specify both a <RawData> document, and fields such as <Title>, <Description>, etc. The binary document will be processed, and any other fields provided will override the values that came from the document.

This can be useful in situations where you have a Content Management System (CMS) that contains metadata about a document that doesn't actually occur anywhere in the document. You can do a custom dataload that pushes in the document, and the custom Title/Description/etc.

Parametric Fields

Each profile-specific Parametric Search field is optionally sent in a single element named after the field, with the XML namespace prefix u. The value of the field is the content of the XML element. Note that the u XML namespace prefix should be declared in the root <ThunderstoneReplication> node, as shown earlier.

Set-type Parametric Search fields should use multiple <value> children to indicate multiple values.

For example, an Integer field Quantity, a GMLPoint field Location, and a Set field Color may be given as:

<u:Quantity>57</u:Quantity>
<u:Location>47.4500 -122.3000</u:Location>
<u:Color>
    <value>Orange</value>
    <value>Black</value>
    <value>White</value>
</u:Color>