> 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/pdi-transformation-steps-reference-overview/get-rows-from-result.md).

# Get rows from result

This step returns rows that were previously generated by another transformation in a job. The rows were passed to this step using either the [Copy rows to result](http://wiki.pentaho.com/display/EAI/Copy+rows+to+result) step or the [Transformation Executor](https://docs.pentaho.com/pdia-data-integration/pdi-transformation-steps-reference-overview/transformation-executor.md) step. You can enter the metadata of the fields you are expecting from the previous transformation in a job.

{% hint style="info" %}
This step produces one or more rows and cannot be placed within an existing stream. It must be the first step in a stream because it produces rows.

If you want to add this data to an existing stream, use a join step.
{% endhint %}

### Step name

* **Step name**: Specifies the unique name of the Get rows from result transformation step on the canvas. You can customize the name or leave it as the default.

### Fields

Use the **Fields** table to enter the metadata of the fields you expect from the previous transformation.

| Column        | Description                                                                                                                                                                                                                |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Fieldname** | Name of the field that contains the rows from the previous result.                                                                                                                                                         |
| **Type**      | <p>Type of data. Options include:</p><ul><li>Number</li><li>String</li><li>Date</li><li>Boolean</li><li>Integer</li><li>BigNumber</li><li>Serializable</li><li>Binary</li><li>Timestamp</li><li>Internet Address</li></ul> |
| **Length**    | <ul><li>For a field with the type of Number, enter the total number of significant figures in a number.</li><li>For a field with the type of String, enter the total length of the string.</li></ul>                       |
| **Precision** | For a field with the type of Number, enter the number of floating point digits. Otherwise, leave blank.                                                                                                                    |

**Note:** There is no validation performed on this metadata. It is intended as a design-time aid.

### Metadata injection support

This step supports metadata injection. You can use it with [ETL metadata injection](https://docs.pentaho.com/pdia-data-integration/pdi-transformation-steps-reference-overview/etl-metadata-injection.md) to pass metadata to your transformation at runtime.


---

# 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/pdi-transformation-steps-reference-overview/get-rows-from-result.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.
