We need the ability to use different date properties for different objects within the same multi-object report.
Current limitation:
In joined reports, the reporting logic is effectively shared across the report, which means monthly totals become inaccurate when each object should be measured by a different date field.
Example use case:
We report on Tickets and a custom object called Heat Pumps in the same report.
What we need is:
- Tickets counted by Ticket create date
- Heat Pumps counted by Commissioned date
Today, if we try to combine these into one report, the date logic does not stay independent per object, so the monthly totals no longer match the standalone reports.
Why this matters:
For operational reporting, this creates misleading results.
The joined report looks like a single source of truth, but the totals are not accurate because each object should follow its own reporting date logic.
Requested enhancement:
Please allow multi-object reports to support:
- an independent date property per object/data source
- separate time-based aggregation logic within the same chart/report
- accurate monthly totals that match each object’s standalone report logic
Ideal outcome:
A single report where:
- Ticket values are grouped by Ticket create date
- Heat Pump values are grouped by Commissioned date
- both can appear in one visual/report without forcing one shared date basis
Cheers,
Louis.