2019.1

Table Of Contents
"CustomerID='CURD654321'");
/* Update Values */
repoObject.SetValueByID("customers", "FormOfAddress", "Mr.",
keySetID);
repoObject.SetValueByID("customers", "Country", "US", keySetID);
repoObject.SetValueByID("customers", "Language", "EN", keySetID);
Version
Returns the version of the DLL library used by the Repository.
Syntax
Version(): string
Metadata API
The "Metadata" on page73 is a hierarchical structure describing the data in a job. It is
composed of 5 basic levels, from top to bottom: Job, Group, Document, Datapage, and Page.
There is a set of plugins that allow to edit the Metadata during a Workflow process (see
"Metadata Tasks" on page545), but you can also manipulate the Metadata in your process via
scripts using the Metadata API.
In the Metadata API, each unit, on all levels in the hierarchy, is represented by an object called
a "Node" on page204.
A Node item is a collection of its lower level node type items. At the top of this tree sits a single
Node object named "MetaJob" on page189. The MetaJob is a collection of "MetaGroup" on
page192 objects, where each MetaGroup is a collection of one or more "MetaDocument" on
page195 objects. In turn, MetaDocument objects hold "MetaDatapage" on page199 objects,
which have "MetaPage" on page202 objects.
In addition, a Node contains a collection of "Attributes" on page221 and can contain any
number of "Fields" on page230.
All of these objects are contained in a "MetaFile" on the facing page object, and they are
obtained, directly or indirectly, through methods of this object.
Note
In an OLConnect job, only the first three levels in the Metadata hold information about the job:
Page 186