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

# Fields panel

This panel includes **Fields** table for specifying the fields that are written to the Excel files. The **Fields** table contains the following columns:

| Column                            | Description                                                                                                                                                                            |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**                          | The name of the field.                                                                                                                                                                 |
| **Type**                          | The data type of a field: String, Date, or Number.                                                                                                                                     |
| **Format**                        | The Excel format to use in the sheet. Please consult the Excel manual for valid formats. There are some online references as well.                                                     |
| **Style from cell**               | A cell in the Excel spreadsheet (letter column, number row) such as `A1`, `B4`, etc., to copy the styling from for this column. This value is usually a pre-styled cell in a template. |
| **Field title**                   | If set, this is used for the Header/Footer instead of the Kettle field name.                                                                                                           |
| **Header/Footer style from cell** | A cell to copy the styling from for the Header/Footer (usually some pre-styled cell in a template).                                                                                    |
| **field contains formula**        | <p>Set to <code>Yes</code> if the field contains an Excel formula.</p><p>You do not need to include the notation <code>=</code> before your field value.</p>                           |
| **Hyperlink**                     | A field that contains the target to link to. Supported targets can be links to other Excel spreadsheet cells, website URL's, ftp's, email addresses, or local documents.               |
| **Cell comment (XLSX)**           | The XLSX format allows to put comments on cells. If you would like to generate comments, you may specify fields holding the comment and author for a given column.                     |
| **Cell comment author (XLSX)**    | The XLSX format allows to put comments on cells. If you would like to generate comments, you may specify fields holding the comment and author for a given column.                     |


---

# 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/microsoft-excel-writer/options-microsoft-excel-writer/content-tab/fields-panel.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.