> 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/pba-report-designer/9.3-report-designer/report-designer-and-reporting-engine-issues-cp.md).

# Report Designer and Reporting engine issues

Follow the suggestions in the following sections to help resolve common issues with Report Designer and the Pentaho Reporting engine:

* [Report elements with dynamic heights overlap other elements](#report-elements-with-dynamic-heights-overlap-other-elements)
* [Columns unexpectedly merge when exporting to Excel](#columns-unexpectedly-merge-when-exporting-to-excel)

## Report elements with dynamic heights overlap other elements

If you have overlapping elements in your report when using the **dynamic-height** style property, use the following directions to create a two-row details band:

1. In the **Structure** pane, select your **Details** band and then go to the **Style** pane and change the value of **layout** to **'block'**.
2. Right-click the **Details** band, then select **band** from the **Add Element** context menu.
3. Move or add the elements for the first row into your created band.
4. Add another band, then move or copy all elements for the second row into the second band.

When your first row elements expand, your second row elements will be pushed down. Repeat this process as necessary for multiple rows.

## Columns unexpectedly merge when exporting to Excel

If you export content from Report Designer to Excel and end up with unexpectedly merged columns in the output, you probably have a horizontal alignment problem with your column header or footer labels. If a label spans two columns, then the Pentaho Reporting engine will force the two columns to merge in the output.

Check your horizontal elements for overlapping column. If you need more information on this topic, refer to the section: [Align elements](https://docs.pentaho.com/pba-report-designer/9.3-report-designer/add-report-elements-in-report-designer-cp.md).


---

# 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/pba-report-designer/9.3-report-designer/report-designer-and-reporting-engine-issues-cp.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.
