Native Salesforce dashboards have significant aggregation limitations that force teams to build external data pipelines just to display basic counts and summaries. This is a known platform constraint — Salesforce acquired Tableau and subsequently deprioritized improvements to their native dashboard tooling, steering customers toward Tableau for advanced reporting.
The practical result: simple operations like "count the items in this list" are not possible natively, requiring workarounds that add complexity and fragility.
Salesforce's native dashboards cannot perform basic aggregations on arbitrary report data — counting records in a filtered list being the most common example. Standard reports can display lists and some metrics (opens, clicks, scheduled sends), but computed counts or cross-object aggregations often fall outside what the native dashboard builder supports.
"There's no way to get this number in Salesforce. No way. Like, you can't do it. Like, all the reports and stuff, they just don't work."
— Mark Hope, 2026-03-04 sync
When native dashboards fall short, the pattern that has emerged is:
This allows the final dashboard to display the computed number as if it were native, while the actual math happens outside Salesforce entirely.
This pattern was implemented for the PaperTube account. See also the related Apex scripting workaround required to make Salesforce Account Engagement (Pardot) behave as expected for that same client.
Salesforce's acquisition of Tableau created a product strategy misalignment: native dashboards stopped receiving meaningful investment, but Tableau licensing is a significant additional cost most mid-market clients won't absorb. The result is a capability gap that falls squarely on implementation teams to bridge.
Salesforce Account Engagement (formerly Pardot) is priced at approximately $12,000/year, which similarly pushes clients toward workarounds rather than native tooling. See [1] for the broader pattern.