Data Types in Data 360

Possible values are ‘true’, ‘false’, and blank.

Fields with boolean data type can’t be used as primary keys, record modified fields, and internal organization fields.

Stores a currency value with a fixed scale of 38 and a precision of 18.

You can use multiple currencies and change the default currency at any time.

Each record is associated with a single currency type. In data lake objects (DLO) and data model objects (DMO) a system field captures the currency code associated with the currency values within a given record. The currency code is a three-character ISO code, such as USD, EUR, INR.

You can’t use a currency field as a primary key or record modifier field for engagement data.

Holds the calendar date without a time part or time zone.

Example: yyyy-MM-dd, where yyyy is the year, MM is the month ranging between 1–12, dd is the day ranging between 1–31.

If the incoming data record includes a time part for a field configured as type date, the time part is ignored. For example, the value 01-01-2023 22:00:00 UTC is ingested and stored as 01-01-2023.

A value that can’t be parsed into a date is stored as a null value.

Stores an instant in time expressed as a calendar date and time of day.

A valid datetime must include the time part and time zone. If they’re not included, it’s inferred as 00:00:00 UTC. If the value can’t be parsed into a datetime, it’s stored as a null value.

Abbreviated time zones like CST are considered ambiguous and aren’t part of the ISO8601 standard.

Stores email addresses. The email data type is modeled on the text data type. You can use any valid text value for ingestion into an email data type field. Data 360 doesn’t validate the format.

You can explicitly choose the email data type for a source field if you want it to be treated as an email ID. You can use an email ID field as a primary key but not as an engagement date field.

Formula functions that work with text values accept email data type input. You can convert the text output from these formula functions into an email data type.

Stores numbers with a fixed scale of 18 and a precision of 38.

Scale is the count of digits to the right of the decimal point in a number. Precision is the total count of digits, regardless of the location of the decimal point. For example, the number 123.45 has a precision of 5 and a scale of 2.

If an ingested number is out of the supported range or is a non-numerical value, a null value is stored.

Holds percentage values. The percent data type is modeled on the number data type. Only valid numeric values are accepted for ingestion into a percent data type field.

You can explicitly choose the percent data type for a source field if you want it to be treated as a percentage.

You can use a percent data type field as a primary key but not as an engagement date field or internal organization field.

Formula functions that work with number values accept the percent data type.

Examples of valid values: 34, 87.232, -0.76523

Examples of invalid values: 255%, 83.21 %, 25 Percent

Stores phone numbers. Data 360 doesn’t validate the format of the phone number. The phone data type is modeled on the text data type. Any valid text value is accepted for ingestion into a phone data type field.

You can explicitly choose the phone data type for a source field if you want it to be treated as a phone number. You can use a phone number field as a primary key but not as an engagement date field.

Formula functions that work with text values accept phone data type input. You can convert the text output from these formula functions into a phone data type.

Stores any kind of text data. It can contain both single-byte and multibyte characters that the locale supports.

Zero length strings (“”) and no value are treated as empty strings.

You must make sure that text fields such as file name, wildcard, directory name, or formula syntax editor use ASCII characters. UTF-8 sometimes contains non-ASCII characters that aren’t guaranteed to work properly. Also, don't use : (colon) and ' (single quote) in file names and formulas. The maximum supported limit for Text field values is 31,072 characters. While this is the maximum limit that Data 360 is certified to support, it isn't a hard limit.

Stores URL values. Data 360 doesn’t parse or interpret the ingested URL value. It also doesn’t validate the value for correctness. Data 360 doesn’t store any metadata related to the URL.

You can explicitly choose the URL data type for a source field if you want it to be treated as a URL. You can use a URL field as a primary key but not as an engagement date field.

The URL data type is modeled on the text data type. Any valid text value is accepted for ingestion into a URL data type field.

Formula functions that work with text values accept URL data type input. You can convert the text output from these formula functions into a URL data type.