2022.2

Values could be retrieved in JavaScript as follows:
var foo = record.fields.ID;
var bar = record.tables.detail[0].fields.ItemTotal;
Data Repository
The Data Repository is a permanent structure to store data that can then be reused, modified or aug-
mented at a later time, by different processes.
This feature was introduced in version 8.5.
The Data Repository is especially useful in situations where data needs to be kept in between pro-
cesses. A few examples:
l
An HTTP-based authentication process, once it has validated user credentials, could store ses-
sion information (unique ID, user name, session starting time) into the repository. All other
related processes could then look into the repository to determine if a new request is received
from an already authenticated user, if the session has expired, what the user name is, etc.
l
Data comes in and is merged into a Capture OnTheGo template and stored in the Data Repos-
itory. The end-user augments the data (using the COTG as a data-entry system). The process
that receives the augmented data could look into the Data Repository to retrieve the original data
(or the ID of the original data records) in order to augment, modify or delete it.
Structure
As can be seen in the "Data Repository Manager" on page710, the Data Repository consists of
Groups, Keys and KeySets.
Feature Name Description Equivalent Database Terminology
Group
A Group is defined by its Keys (columns), and may contain 0 or
more KeySets (rows) within it.
Table
Key
A Key is defined only by its name. The Data Repository only
supports STRING values and any data inserted into it is con-
verted to string automatically. The maximum size of a single
key is 1 billion bytes.
Column/Field
KeySet
A group may contain as many KeySets (rows), which contain
variable data, as necessary. A KeySet is inserted using the
"Push to Repository" on page393 task.
Row/Record
Lookup
A method of retrieving one or more KeySets from a group in
the data repository.
Query
Page 80