Thanks for reporting this @pbb72 👍

It would certainly be better if the totals row correctly reflected the displayed rows. I'll pass this on to our product team for prioritization.

Another user asked for this also:

Feature: Pages
Like: No
Feedback:
If I filter the table data via the search input at the bottom of the table the row containing the totals does not update accordingly to the entered query and still show the totals of all pages.
Please also note, that the feature "Aggregated rows are displayed" is activated.
Thoose values should be excluded from the totals, otherwise this data would be counted twice.
By the way: it seems to be a general problem not only for page views.

Another user is facing a similar issue. When the report is flattened, the totals are not refreshed in dashboard; it shows the total for the hierarchical report. You need to export the flattened report and summarize the values to see the correct totals.

Either the totals row should show the totals for only the filtered data, or another row should be added to show the totals for only the filtered data.

It's expected behaviour for the totals row to show the sum of all rows. We would need to add another second row that shows the totals for the matched rows.

It's expected behaviour [...]

You state that as if you know every user? I definitely didn't expect this behaviour, otherwise I wouldn't have submitted this bug. Did you mean "intended behaviour" or am I misunderstanding?

@pbb72 Yes, I meant "intended behaviour" 👍 Sorry for the confusion.

Then I think the intended behaviour is wrong (obviously, as I posted this bug report). I still feel a single totals row that displays the totals of the filtered results would be the expected result for most users.

But I guess having two totals rows would be the best of both worlds.

I got a client asking for this today.

We had a user get majorly tripped up by this today.

They have been exporting what they thought was a subset, and reporting to their client a falsely high total because of this bug.

I got a client asking for this feature today.