OrchestratorConfigExplicitTypeDefinitions Property

This setting defines data types used in internal representations of record fields. It contains a set of keys (field names) along with their corresponding data types and optional formats.

The setting is in the form of a comma delimited list of items, each item being a pipe delimited triplet: fldName|type|format, where type is one of: S=String, M=Decimal, D=DateTime, I=Integer, B=Boolean; and format is the format string used when formatting output. Format can be omitted with the preceding pipe, in which case no formatting will take place. Format has no relevance on intake. In addition, with one exception, format is ignored in JSON output, because JSON supports writing elements in their native data types. The exception is for fields of DateTime type, which are not supported in JSON. DateTime fields are converted to strings (respecting format) before being submitted to JSON output.

Example:"AMOUNT|M,BIRTH_DATE|D|M/d/yyyy,AGE|I"

Sequence of the elements in this setting is irrelevant.

Types of the fields not specified in ExplicitTypeDefinitions are determined by the TypeDefiner function, which by default assumes string type and no format for all fields.

Note

In case of JSON or UnboundJSON intake, the elements are parsed according to JSON specifications, which involves automatic data type determination. However, in order to preserve this type, the corresponding field must be of a matching type. Otherwise, the type conversion will be performed. For example, a JSON element "ID": 5 will be parsed as number 5. So, in order to avoid type conversion, a setting of ID|I is needed (otherwise, number 5 will be converted to string "5"). Similarly, an element "ID": "5" will be parsed as string "5". Therefore, no type conversion will take place in absense of type definition for field "ID" (fields are strings by default); if however setting ID|I is present, then string "5" will be converted into number 5.