> 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/row-denormaliser.md).

# Row Denormaliser

The Row denormaliser step can be used to try to improve performance either by adding redundant copies of data values or by grouping data. You can also use this step to convert data types.

**Note:** The data must be normalized before you can denormalize it.

For example, consider the following set of normalized data:

| Produce Category | Delivery Time       | Produce Type |
| ---------------- | ------------------- | ------------ |
| fruit            | 2018/01/05 08:00:00 | apples       |
| fruit            | 2018/01/05 08:10:00 | oranges      |
| fruit            | 2018/01/05 08:20:00 | apples       |
| fruit            | 2018/01/05 08:30:00 | oranges      |

The data can be denormalized by grouping on the type of fruit, as shown in the following table:

| Produce Category | Apples              | Oranges             |
| ---------------- | ------------------- | ------------------- |
| fruit            | 2018/01/05 08:00:00 | 2018/01/05 08:10:00 |
| fruit            | 2018/01/05 08:20:00 | 2018/01/05 08:30:00 |


---

# 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/row-denormaliser.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.