> 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/hierarchical-json-output.md).

# Hierarchical JSON Output

You can use the Hierarchical JSON output step to convert hierarchical data from a previous step into JSON format. For an overview of hierarchical data in Pentaho, see [Hierarchical data](/pdia-data-integration/extracting-data-into-pdi/hierarchical-data.md).

**Note:** This step accepts only hierarchical data.

### Step name

* **Step name**: Specifies the unique name of the Hierarchical JSON output step on the canvas. You can customize the name or leave it as the default.

### Options

![Hierarchical JSON Output step dialog box](https://773338310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYwnJ6Fexn4LZwKRHghPK%2Fuploads%2Fgit-blob-a8f57b4ebc1af678856fe68b91352b92f708e85a%2FPDI%20Hierarchical%20JSON%20Output%20step.png?alt=media)

#### Fields

| Field                        | Description                                                                                             |
| ---------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Input hierarchical field** | Specifies the hierarchical input field name from a previous step which is formatted to the JSON format. |
| **Output field**             | Specifies the step output field to contain the generated JSON output.                                   |

#### Additional options

| Option                     | Description                                                                                                                                                                                                           |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Pass output to servlet** | Select to return the data using a web service instead of passing it to output rows. See [PDI data over web service](https://pentaho-public.atlassian.net/wiki/spaces/EAI/pages/384958757/PDI+data+over+web+services). |
| **Pretty print?**          | Select to format the output JSON data.                                                                                                                                                                                |


---

# 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/hierarchical-json-output.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.