April 21, 2026

Improved the accuracy of Report Builder queries that combine aggregations (sum, count, avg, min, max) on the primary resource with with joins.

Fixed

Reports API / Query API

• Reports that aggregated on the primary resource while also joining another resource — for example, "total spend per requestor per application" (grouping payments by email with with: { applications }) — could previously return too many rows with understated per-row totals. The fix restores the intended grouping. If you have saved reports in this shape, you may now see fewer rows with higher per-row aggregates. These are the accurate values.

Changed

Reports API / Query API

• Queries that use an op field on the primary resource alongside with now require at least one non-op field on the primary to group by. Previously these queries failed with an unclear database error; they now return a 400 Bad Request with guidance:

  When using "op" fields on the primary resource alongside "with", at least one non-"op" field must be provided to group by. Add a non-aggregate field to "fields", or remove "with".