> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/data-management-in-datahub/datasets-in-toucan/preparing-data/overview-of-youprep-tm/column-header/convert-columns-data-types.md).

# Convert columns data types

The Convert columns data types allows to cast column data types.

### Step parameters

* `Convert columns` **column(array)\***: the columns to convert
* `To data type` **type(string)**: the data type to convert into, either `integer`, `float`, `text`, `date` or `boolean`

### Example

**Input**

<figure><img src="/files/5NSelszFKKIszK810IUD" alt=""><figcaption><p>Column header - convert input</p></figcaption></figure>

**Configuration**

```json
{
  "columns": ["id", "boolean_column"]
  "data_type": "text"
}
```

**Output**

<figure><img src="/files/xykpD52FA1uSzCEHesJm" alt=""><figcaption><p>Column header - convert output</p></figcaption></figure>

{% hint style="info" %}
In a effort to harmonize as much as possible the conversion behaviors, for some cases, in NativeSql our implementation casting works otherwise than the CAST AS method.

Precisely, when casting float to integer, the default behavior rounds the result, other languages truncate it. That’s why the use of `TRUNCATE` was implemented when converting float to int. The same implementation was done when converting strings to int (for date represented as string). As for the conversion of date to int, we handled it by assuming the dataset’s timestamp is in `TIMESTAMP_NTZ` format.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-v3.toucantoco.com/data-management-in-datahub/datasets-in-toucan/preparing-data/overview-of-youprep-tm/column-header/convert-columns-data-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
