DC5.0.0 6.6 - Appendix
Datatypes in Digizuite
Datatypeid | Description |
---|---|
51 | Integer |
62 | Datetime |
60 | String |
61 | Bit |
70 | Note (used for description) |
82 | Float |
65 | Metagroup |
59 | Combo (the metafield, not the value) |
52 | MultiCombo (the metafield, not the value) |
68 | ComboValue (value, not metafield) |
67 | MultiComboValue (value, not metafield) |
69 | EditComboValue |
169 | EditMultiComboValue |
300 | Tree |
Datatypes in BatchUpdate
DatetypeId | Description |
---|---|
1 | String |
2 | Bool |
3 | Int |
4 | DateTime |
5 | Float |
6 | IntList |
17 | StringList |
Mapping between Datatypes in BatchUpdate
Digizute Datatype | BatchUpdate DataType | BatchUpdate value example |
---|---|---|
60 | 1 | "test" |
70 | 1 | "test" |
69 | 1 | "test", name of the combo value |
61 | 2 | "1" |
62 | 4 | "mm/dd/yyyy hh.mm.sss" |
67 | 6 | 55, id of the combo value |
68 | 6 | 55, id of the combo value |
168 | 17 | "one", "two" - list of combo values |
51 | 3 | 17, integer |
Other tips and tricks
The Digizuite has the following object heirachies:
Item Asset ComboValue TreeValue MetaField etc...
The means that everything in the Digizuite is an Item, and thus have an ItemId. In addition everything has a BaseId, which is separate from the ItemId. This is why assets can keep counting up in id, one after the other, while the ItemId is skipping ahead several steps.
This means there are 2 kinds of Ids in the Digizuite. The "ItemId" and the "BaseId". The "BaseId" is also sometimes called the "Id".