> For the complete documentation index, see [llms.txt](https://videos.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://videos.inforiver.com/reporting-matrix/graphical-tables/stacked-charts.md).

# Stacked charts

Stacked charts are often used to show the breakdown of a total, such as the distribution of expenses by category or the composition of a portfolio by asset class. They can also be used to show changes in the composition over time, such as the distribution of sales by product or region.

Inforiver offers two variations of stacked charts, they are: 

(a) Stacked chart - where each section of the bar represents the absolute value of each series and

(b) Percentage stacked bar chart - where each section of the bar represents the relative proportions of the data series 

These charts can also be customized - The order of data series can be set to ascending or descending The data labels can be aligned within the bars The axis line can be displayed for reference IBCS, Power BI or custom themes can be applied.​

{% embed url="<https://lumel.wistia.com/medias/6t1ntpgz49>" %}

> ## **Related resources**
>
> #### User guide
>
> [Stacked charts](https://docs.inforiver.com/working-with-inforiver/6.-working-with-charts/stacked-charts)


---

# 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://videos.inforiver.com/reporting-matrix/graphical-tables/stacked-charts.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.