> 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/mapping/mapping-input-specification/options.md).

# Options

| Option                                          | Description                                                                                                                                                                                                                                                        |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Step name**                                   | Name of the step. This name has to be unique in a single transformation.                                                                                                                                                                                           |
| **Name**                                        | The name of the field as it will be known inside the sub-transformation.                                                                                                                                                                                           |
| **Type**                                        | The data type of this field.                                                                                                                                                                                                                                       |
| **Length**                                      | Maximum string length.                                                                                                                                                                                                                                             |
| **Precision**                                   | Maximum number of decimals.                                                                                                                                                                                                                                        |
| **Include unspecified fields, ordered by name** | <p>In certain borderline cases, you not only want the required fields, but all of them. This option allows for this situation.</p><p>This is the case, for example, if you want to remove certain fields from the stream later on, retaining all other fields.</p> |

\*\*Note:\*\* During design time, none of these unspecified fields will be available in field picklists etc., since these fields will be available only during runtime, not design time.


---

# 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/mapping/mapping-input-specification/options.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.