# Dynamic aggregate calculations based on user-filtered date ranges?

**URL:** <https://community.noloco.io/t/dynamic-aggregate-calculations-based-on-user-filtered-date-ranges/2308>\
**Category:** Ask for Help\
**Created:** [December 2, 2025, 12:53pm UTC](https://community.noloco.io/t/dynamic-aggregate-calculations-based-on-user-filtered-date-ranges/2308 "2025-12-02T12:53:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MWorth](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@MWorth](https://community.noloco.io/u/MWorth)\
**Post date:** [December 2, 2025, 12:53pm UTC](https://community.noloco.io/t/dynamic-aggregate-calculations-based-on-user-filtered-date-ranges/2308/1 "2025-12-02T12:53:21Z")

</div>

I’m running into a limitation and wondering how others are handling this (or if I’m missing something obvious).

**The setup:** I have a table with three fields: `sourced`, `taken`, and `load_date`. Easy enough to create a formula field for variance (`sourced - taken`).

**What I need:** I need to calculate percent variance as `(SUM(variance) / SUM(sourced)) * 100` but only across records that fall within a user-selected date range. Basically, the user filters the collection view by `load_date` and I need the aggregated percent variance to reflect only those filtered records.

**The problem:** Rollup fields calculate against all linked records regardless of what’s displayed in the filtered view. I’ve tried creating a rollup table with pre-defined periods (this year vs last year, etc.) but that feels like a poor solution when you start thinking about every month/year combination. The rollups don’t respect UI filters, they’re static calculations.

I understand formula fields work at the record level and rollups work against linked records, but is there any pattern people are using to get true dynamic aggregation based on user-applied filters?

Anyone found a clean solution for this? Or is this just a current gap in the platform?

---

<div class="post-metadata">

**Author:** ![MWorth](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@MWorth](https://community.noloco.io/u/MWorth)\
**Post date:** [December 2, 2025, 1:38pm UTC](https://community.noloco.io/t/dynamic-aggregate-calculations-based-on-user-filtered-date-ranges/2308/2 "2025-12-02T13:38:44Z")

</div>

I’m thinking a compromise will be to have a Make automation build yearly, quarterly, monthly “rollup” tables that are triggered either by the user or by schedule. Then I could limit the filter selection of the user on the dashboard to these options in the table.
