> 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/microsoft-excel-input/options-microsoft-excel-input/fields-tab.md).

# Fields tab

![Microsoft Excel Input step Fields tab](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-e753c621a35c91bb7e985c60e787f125e782512b%2FPDI_TransStep_Microsoft_Excel_Input_Fields_Tab.png?alt=media)

The **Fields** tab shows field definitions for extracting values from the Microsoft Excel spreadsheet. The table in this tab contains the following columns:

| Column        | Description                                                                                                                                                                                                                                                                          |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Name**      | Name of field that maps to the corresponding field in the Microsoft Excel Input stream.                                                                                                                                                                                              |
| **Type**      | Data type of the input field.                                                                                                                                                                                                                                                        |
| **Length**    | Length of the field.                                                                                                                                                                                                                                                                 |
| **Precision** | Number of floating point digits for number-type fields.                                                                                                                                                                                                                              |
| **Trim type** | The trim method to apply to a string.                                                                                                                                                                                                                                                |
| **Repeat**    | The corresponding value from the last row repeated if a row is empty.                                                                                                                                                                                                                |
| **Format**    | An optional mask for converting the format of the original field. See [Common Formats](/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/common-formats.md) for information on common valid date and numeric formats you can use in this step. |
| **Currency**  | Currency symbol (`$` or `€` for example).                                                                                                                                                                                                                                            |
| **Decimal**   | A decimal point can be a "`.`" (`5,000.00` for example) or "`,`" (`5.000,00` for example).                                                                                                                                                                                           |
| **Group**     | A grouping can be a "`,`" (`10,000.00` for example) or "`.`" (`5.000,00` for example).                                                                                                                                                                                               |

Click **Get fields from header row** to have the step populate the table with fields derived from the source file. All fields identified by this step will be added to the table.

See [Understanding PDI data types and field metadata](/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/advanced-topics-pdi-perspective/understanding-pdi-data-types-and-field-metadata.md) to maximize the efficiency of your transformation and job results.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/microsoft-excel-input/options-microsoft-excel-input/fields-tab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.