Discrepancy in Row Count Between Two Tables

giannzi

Hi,

I created two Mega Tables with the exact same filters, but they are returning different row counts. The first table shows only 8 rows, while the second table returns 28 rows.

The only difference initially was that the first table was originally an HTML table, and one of its columns was based on a Beast Mode calculation. I expected it to return 28 rows, but it didn’t. To troubleshoot, I converted it to a Mega Table and removed the Beast Mode calculation to match the second table exactly. However, it still only returns 8 rows.

I’ve also verified that the date ranges are the same. At this point, both tables are identical in structure, filters, and settings—yet they still return different row counts. Any idea why this is happening?

DavidChurchman

• If you switch it back to an HTML table, are there any settings not turned to default? Sometimes when you switch between card types, you can check off a setting that still applies to other card types, even if that setting doesn't appear in the menus.

My other thought it that maybe one of the cards is on a "view" of the data and not the data itself. Are the datasets truly identical?

Mr_Miyagi

Sounds like an aggregation issue. Verify your Aggregation in Sorting and on the Columns section are set to "No aggregation" if you want to display your 28 rows. If you use any aggregation function via beast mode like COUNT() then it will be set to count.