Metabase Datatypes
4/8/2010
The OMA DM Format property is called a datatype in the metabase. The datatype specifies the node value.
The following table lists the datatypes.
| Datatype | Description |
|---|---|
int |
Integer. Whole number values. These values are translated by the OMA DM Data Process Unit (DPU). |
chr or string |
Character. Character datatype in OMA DM is equivalent to string datatype in OMA Client Provisioning, and is translated by the DPU. |
bin |
Binary. Binary as an octet stream. Often encoded as b64. |
float |
Floating point. This is a numeric floating point value. > [!NOTE] > Float datatype is supported in Windows Mobile for OMA Client Provisioning protocol, but not for OMA DM protocol. |
bool |
Boolean. This value is translated by the DPU. |
null |
Null. An empty value. |
node |
An interior node. |
b64 |
Base64 encoded. b64 is not a valid datatype in the Metabase. b64 is supported in OMA DM packages transmitted between client and the server. The b64 encoded data is stored in the device as binary datatype. |
mchr |
Multistring. Microsoft extended multistring datatype. MultipleString data type is treated as character format in OMA DM. Each string is terminated with Unicode 0xF000. |
time |
Time. The time format is ISO 8601 format. Both time only and the combination of date and time are supported. If the date + time format is used then a 'T' must appear between the date and time. The following ISO 8601 time formats are supported:
When you query a time format node, the Universal Time (UTC, also known as GMT, or Greenwich Mean Time) format is returned regardless whether it is created or replaced with UTC or local time that includes time zone information |
date |
A date. The date format is ISO 8601 format with the century being included in the year. The following ISO 8601 date formats are supported:
The supported date range is from January 2nd, 1753 to December 31st, 2078. |