> 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/10.2-data-integration/pdi-transformation-steps-reference-overview/row-flattener/example.md).

# Example

Suppose your file contains company order information and has one attribute per row as shown below. In the file, each order is described in three rows: one row for the name of the company, one for the country, and one for the order number:

```
Land of Toys Inc.
United States
10107
Lyon Souvenirs 
France
10134
Australian Gift Network, Co
Australia
10374
Gift Depot Inc.
```

Using the following entries in the Row flattener step, the rows are flattened into three target fields:

![Row flattener entry example](/files/QVqSytUR9FNopIYxO8Pi)

The resulting data set is shown below. For every three rows, the data is now formatted into a single row.

![Results example for Row flattner](/files/wR9scNy8xuMw4UMzMcUf)

**Note:** Incomplete or non-consecutive data can lead to unexpected 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 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/10.2-data-integration/pdi-transformation-steps-reference-overview/row-flattener/example.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.