Pivot Table Expand and Collapse Inconsistency

Hi there,
I have recently found out that when I'm using Pivot Table, there is inconsistency on the data that is being displayed when I expand and collapse the columns. Here is the example:

So in the image above, I have following columns : DateOrdered, C_BPartner_ID, M_Product_ID and Sum of QtyOrdered. I'm looking at the data from February 2002 which has 2 C_BPartner : 112 and 114. Notice that 114 has two Product (123 and 130) and 112 only has 1 (130). Everything looks good here.

When I collapse the C_BPartner_ID column, it shows 114 only as the C_BPartner and Sum QtyOrdered 20, meanwhile the total for February 2002 has total of 23 ( because there is transaction with C_BPartner 112 as well).
Any idea why is this happening?

Here's my diagnostic info: ( I'm using H2 as the database, because I'm setting up new server in local to test out the bug , I'm using Postgres at production)
"browser-info": {
"language": "en-US",
"platform": "Linux x86_64",
"userAgent": "Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0",
"vendor": ""
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.16+8-post-Debian-1deb11u1",
"java.vendor": "Debian",
"java.vendor.url": "openjdk-11 - Debian Package Tracker",
"java.version": "11.0.16",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.16+8-post-Debian-1deb11u1",
"os.name": "Linux",
"os.version": "5.10.0-17-amd64",
"user.language": "en",
"user.timezone": "Asia/Jakarta"
"metabase-info": {
"databases": [
"hosting-env": "unknown",
"application-database": "h2",
"application-database-details": {
"database": {
"name": "H2",
"version": "1.4.197 (2018-03-18)"
"jdbc-driver": {
"name": "H2 JDBC Driver",
"version": "1.4.197 (2018-03-18)"
"run-mode": "prod",
"version": {
"date": "2022-08-31",
"tag": "v0.44.2",
"branch": "release-x.44.x",
"hash": "8d9de8a"
"settings": {
"report-timezone": null

Hi @vincentparuh
I've created an issue for it:
https://github.com/metabase/metabase/issues/25250 - upvote by clicking :+1: on the first post

Separately, you should migrate away from H2 if you're using Metabase in production: