> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/desktop-client/reporting/remove-empty-elements.md).

# Remove empty elements

Generate and customize detailed reports in the desktop client. Learn step-by-step reporting features, settings, and export options to enhance your data analysis workflow.

In aqua reports, you can iterate on different elements. It may be that there is a scenario where all requirements are iterated. So, you can have a header and all requirements should be listed. But there may be a special case where no requirements are listed in the reports. So, you want to show those elements. In the following, you will receive information about how to solve this problem by setting the elements to invisible. To do so, open a band as shown in the following screen.  

<figure><img src="http://aquawiki.andagon.com/pictures/drex_remove_empty_elements_custom.png" alt=""><figcaption></figcaption></figure>

A context menu opens. Here, click on Formatting Rules. A new window is opened, click on Edit Rules. Here, you can create a new rule.

<figure><img src="http://aquawiki.andagon.com/pictures/drex_remove_empty_elements_custom_2.png" alt=""><figcaption></figcaption></figure>

&#x20;&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_remove_empty_elements_custom_3.png" alt=""><figcaption></figcaption></figure>

&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_remove_empty_elements_custom_4.png" alt=""><figcaption></figcaption></figure>

Confirm by clicking on OK, click on Close and add rule to band. &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_remove_empty_elements_custom_5.png" alt=""><figcaption></figcaption></figure>


---

# 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.aqua-cloud.io/documentation/desktop-client/reporting/remove-empty-elements.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.