> 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/reporting/exclude-empty-items-from-a-report.md).
# Exclude empty items from a report
No report data to display? Learn how to automatically exclude empty items from your reports for clearer, more relevant results. Step-by-step guidance included.
In aqua reports, you have the flexibility to iterate through various elements. There might be scenarios where all requirements need to be iterated, resulting in a report header and a list of all requirements. However, there could be exceptional cases where no requirements should be displayed in the reports. In such instances, you may want to hide these elements. Below, you will find instructions on how to address this issue by setting elements to be invisible.
Begin by selecting the band you wish to conceal if there are no printable items. Then, choose 'Properties' and navigate to the 'Behavior' settings
Navigation to the 'Visible' settings
To create a new expression please select the  icon and then 'Visible Expression' -> 'Before Print',
You can now define a name and a condition. For example, you can navigate to the 'Variables' section and select the 'Data.Source.RowCount' variable, which returns the total number of rows in a data source. If the count is 0, then the band will not be printed on the report.
Example of condition that excludes blank items from printing
---
# 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/reporting/exclude-empty-items-from-a-report.md?ask=&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.
