> 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/python-executor/options-python-executor/input-tab/row-by-row-processing.md).

# Row by row processing

Select the **Row by row** option to process your data row by row. Each input row will have its fields mapped to the variables as defined in the **Mapping** table, below. Your Python script will be executed once for each incoming row.

**CAUTION:**

When using the PDI Engine, you can include multiple input steps of the same schema. Each input step must have the same field structure, such that fields and types must appear in the same order in each incoming step. If you include multiple input steps of different schema, an error will occur.

![Input tab in Python Executor](/files/YVwkznfU0e1lAx0HTpL9)

The **Mapping** table contains the following field properties.

| Field Property       | Description                                                                                                                                                                                                                                                                                                                                                                                          |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Variable**         | String assigned as a Python variable.                                                                                                                                                                                                                                                                                                                                                                |
| **Python data type** | The Python data type assigned to the variable, such as a string (‘str’), an integer (‘int’), or a floating point (‘float’). For detailed information on data types, see [Mapping data types from PDI to Python](/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/python-executor/options-python-executor/input-tab/mapping-data-types-from-pdi-to-python.md). |
| **PDI field**        | The PDI field to which you want to map the Python variable.                                                                                                                                                                                                                                                                                                                                          |
| **PDI data type**    | The data type assigned to the PDI field, such as a date, a number, or a timestamp.                                                                                                                                                                                                                                                                                                                   |

Select the **Get fields** button to populate the table with fields from the input step(s) in your transformation. If necessary, you can modify your selections.


---

# 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/python-executor/options-python-executor/input-tab/row-by-row-processing.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.