Supported Data Types

Data types in Decision Tables

All data in a decision table is stored as string values and is automatically cast when needed. Therefore, you don’t need to specify any data format for your input and output models. The automatic casting of conditions and results is described in the following sections.

The decimal separator is always a dot: 5.5

Condition Data Types

Conditions can be created using the following scalar data types:

Number
Boolean
String
Date

Conditions

Solver Request Data Example

The inputs below demonstrate the format in which you can send a request to match a particular row:

Number:

{
  "input": "2.31"
}

{
  "input": 2.31
}

Boolean (True):

{
  "input": true
}

{
  "input": "true"
}

Boolean (False):

{
  "input": false
}

{
  "input": "false"
}

String:
```
{
  "input": "hello world"
}
```

Date and Time:

{
  "input": "2024-09-23 13:27 +02:00"
}

or as extended ISO-8601:

{
  "input": "2024-09-23T13:27:00+02:00"
}

Empty Value:
```
{
  "input": ""
}
```

The data cells now convert dates to strings. The old object format is deprecated but still supported. For example, the input:

{
"input": {
    "date": "2024-09-23",
    "time": "13:27",
    "timezone": "+02:00"
    }
}

will match the new condition 2024-09-23 13:27 +02:00.

Read more about Date cells in the dedicated section.

Examples:

Calculation Data Types

Calculation columns support all the data types used by result columns.

Result Data Types

When calling the Solver API, the response returns an array of results based on the decision table setup. Response values are automatically cast to the following data types:

Boolean
Number
String
Date
JSON Object
JSON Arrays

Casting examples:

Last updated 1 month ago