Absolutely maddening reporting requirements, I think I'm almost there though - help!

Hi all — jumping in with a possible workaround for the “Distinct Count counts null as 1” issue.

From what I’ve seen, there aren’t a ton of clean ways to exclude nulls from a Distinct Count at the Interaction level without shifting the logic somewhere else (like filtering, rolling up from parent relationships, or using formula queries — which may get heavy if you’re doing this across a large dataset).

One idea that might be a simple/low-maintenance hack: Create one dummy Interaction record where the fields you’re doing distinct counts on are intentionally null/blank (across the relevant helper fields).

Then in reporting, use Distinct Count minus 1 as your final displayed total (via a summary variable).

Since null is only one distinct value, this effectively removes the “null = 1” inflation without needing to filter out records (and accidentally impacting other counts), or build out additional parent-table rollups.

If anyone’s done something cleaner, I’d love to hear it — but this feels like a pretty contained workaround that keeps the Interactions table as the single source of truth.