> For the complete documentation index, see [llms.txt](https://brixxbox.gitbook.io/brixxbox-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brixxbox.gitbook.io/brixxbox-documentation/app-erstellung/how-tos/telerik-extension-functions/telerik-page-footer-sum.md).

# Telerik Page Footer Sum

How to use brixxbox custom functions in telerik

### BrixxPageFooterSum

Sums elements in a table up to this footer

{% hint style="info" %}
Each page sum function can only be used once in a report. Using it multiple times will result in wrong calculated values!
{% endhint %}

### Demo

```javascript
//This function belongs in a PageFooterSection of a telerik report
=PageExec("textBoxValue",             //put in a textbox from your table row. Typically your value textbox, but whatever is in your row will work. This triggers the accumulation of the values
           BrixxPageFooterSum(
               Fields.yourValue,      //put in the Value Field you want to sum up
               ReportDefinition))     //this is fix (it will tell the sum to reset for each new report)
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://brixxbox.gitbook.io/brixxbox-documentation/app-erstellung/how-tos/telerik-extension-functions/telerik-page-footer-sum.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 `build a script that syncs our docs to a CMS` 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.