🐞 Description of the issue: When using a table chart with row grouping enabled and activating the "Show total summary" option, the summary row (e.g., sum, count) reflects the total for the entire dataset, not just the rows currently displayed in the chart.
This can be confusing, especially when the dataset is large or when filters/pagination are applied, because the visible data doesn't match the summary shown.
📌 Steps to reproduce: Create a table chart using a dataset with multiple rows.
Enable group by on a column (e.g., category or region).
Enable "Show summary row" in the chart settings.
Apply filters or scroll through paginated views.
❌ Problem: The summary row displays totals for all data returned by the query, not only for the visible rows on screen.
It creates a mismatch between what the user sees and what the summary shows.
✅ Expected behavior: The summary should either:
Reflect only the visible rows in the current page/group, or
Include an indicator that it shows totals for the full dataset.
Comment From: dosubot[bot]
I found a similar unsolved discussion titled Totals in table charts, which might be relevant to your issue [1].
Regarding your issue, the current behavior of the "Show summary row" feature is to display totals for the entire dataset when formData.show_totals is enabled and the query mode is QueryMode.Aggregate. This is because an extra query is created for total aggregation, which does not apply pagination or filtering to the results [2].
To address your concern, you might consider implementing a mechanism to differentiate between totals for visible rows and totals for the entire dataset. This could involve modifying the query logic to apply filters and pagination to the summary calculations, or adding an indicator to clarify that the summary reflects the entire dataset.
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
Comment From: rusackas
Curious if the discussion Dosu linked to makes sense for this. Not sure if it's really a bug or if the tooltip mentioned somewhat mitigates the situation.
Comment From: ryepezb1
Tengo curiosidad por saber si la discusión a la que Dosu hizo referencia tiene sentido. No sé si se trata de un error o si la información sobre herramientas mencionada mitiga la situación. I feel the same way. Are you seeing the same error I mentioned?
I think the tool should give us the option to decide what to do with grouped column values — whether to sum, average, etc.
I’m referring specifically to the values shown on screen in the grouped table, not the entire dataset.
When I enable "sum" on a column, yes, it calculates the total — but it’s summing from the entire dataset, not from the grouped/visible rows I see.
Not sure if I’m explaining it clearly, but ideally it should be possible to summarize only what’s visible on screen (based on current filters or groupings), not the full data in the backend.
Comment From: vivek-kandhvar
@dosu Any update on this issue?
Comment From: dosubot[bot]
There haven't been any changes to how summary rows work in table charts. The summary row still always shows totals for the entire dataset, not just the visible or grouped rows—even when filters or pagination are applied. This is by design and is clarified in the UI with a tooltip. There are no open tickets or recent code changes to support summarizing only visible/grouped rows; implementing that would require new architectural and UI/UX work. If you need percentage metrics based on visible rows, there is a new option for that, but it doesn't apply to summary totals yet (details).
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
