> 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/pentaho-analyzer-cp/set-analyzer-report-options/options-for-totals.md).

# Options for totals

By default, grand totals do not display when you view a report as a pivot table. Also, totals never display when you view a report in chart format.

Below are the options for showing and hiding grand totals for rows and columns.

* **Grand totals for rows**

  Select to display grand totals for rows in your report.
* **Grand totals for columns**

  Select to display grand totals for columns in your report
* **Totals with filtered values**

  Select to display totals which include [filtered values](/pba/pentaho-analyzer-cp/adding-filters-to-an-analyzer-report/add-filters-to-an-analyzer-report.md). By default, totals only display the sum of the values which are visible on the report. If you want to see a total that includes the values that are filtered out, right-click on the **Grand Total** cell in the report and select **Display Totals that Include Filtered Out Values** from the menu.
* **Totals on top/left**

  Select to display totals at the top for column totals and on the left for row totals in a pivot table. Typically, totals appear at the bottom of columns and at the end of rows.

To hide grand totals while viewing a report as a pivot table, right-click the **Grand Total** cell on the report, and select **Hide Grand Total** from the menu. This method does not allow you to show grand totals again once it is hidden.


---

# 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/pentaho-analyzer-cp/set-analyzer-report-options/options-for-totals.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.