> 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/sum-function.md).
# 'Sum' function
Easily sum or count data in report labels and tables - no scripting needed. Configure summary settings for group, report, or page totals directly in the properties panel.
The Sum function for a label or table cell allows you to collect data from different elements. This function allows you to perform a simple count of the number of items without having to use scripts.
To do this, go to the properties of a field in the Data section and select Summary. In the running field, you can choose to total only the group, the whole report or each page.
In the Run Editor (white box next to the summary) you can then select the function, i.e. whether you want the summary to be summed, counted (number) or other groupings.
Navigating to the Run Editor
Accessing the Expression Editor
Using respective formula fields (for example, “If output 0/1” (see formula below)), you can calculate characteristic values for elements.
{% code overflow="wrap" %}
```
Iif([LastExecutionStatusInvariant]=='Passed', 1, 0)
// all test cases with the status “Passed”
```
{% endcode %}
Utilizing Expression Editor
---
# 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/sum-function.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.
