> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/catalog-input/general-catalog-input/fields-tab-catalog-input/csv-fields-catalog-input.md).
# CSV fields
When CSV data is read, the table defines the fields to read as input from the CSV file.
Enter the information for the Catalog Input step fields as shown in the following table.
| Column | Description |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | The name of the field. |
| **Type** | The data type of the field. |
| **Format** | Enter the number format. See [Number formats](/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/hadoop-file-input-cp-main-page/select-an-engine-hadoop-file-input/using-the-hadoop-file-input-step-on-the-pentaho-engine-cp/options-hadoop-file-input-reuse/fields-tab-hadoop-file-input-reuse/number-formats-hadoop-file-input-reuse.md) for a description of format symbols. |
| **Position** | The position is needed when processing the 'Fixed' **Filetype**. It is zero based, so the first character starts with position ‘`0`’. |
| **Length** | The value of this field depends on the format:
- Number: Total number of significant figures in a number.
- String: Total length of the string.
- Date: Length of printed output of the string. For example, ‘
4’ only returns the year.
|
| **Precision** | The value of this field depends on the format:
- Number: Number of floating point digits.
- String, Date, Boolean: Unused.
|
| **Currency** | Used to interpret the symbol used to represent currencies (for example, `$` or `€`). |
| **Decimal** | Used to represent a decimal point, either a dot '`.`' or a comma '`,`' (for example, `5,000.00` or `5.000,00`). |
| **Null if** | Used to set as null (empty) if the string is equal to the specified value. |
| **Default** | Used to specify a default value to use in case the field in the CSV file was not specified (empty). |
| **CatalogType** | The data type as defined in Data Catalog. For example, `UTF8`. |
| **Get Fields** (button) | Click to retrieve a list of fields derived from the source file in Data Catalog. |
| **Minimal width** (button) | Click to minimize the field length by removing unnecessary characters. If selected, string fields will no longer be padded to their specified length. |
---
# 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.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/catalog-input/general-catalog-input/fields-tab-catalog-input/csv-fields-catalog-input.md?ask=&goal=
```
`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.