Description: We’d like the ability to build time-series reports where the X-axis is a date (e.g., month-year) and the Y-axis shows multiple lines based on different date properties from the same object. Today, in the custom report builder, the X-axis can only use one date property at a time. That means we can’t directly compare two different date properties as separate lines on the same time axis. Example from our use case: On our customers (or deals), we track two custom date properties: Target Go Live Date Expected Go Live Date What we want is a line chart where: The X-axis is grouped by month-year The Y-axis shows, for each month, counts based on: Line 1: records with a Target Go Live Date in that month Line 2: records with an Expected Go Live Date in that month This would let us see visually, over time, how our “target” timelines compare to our “expected” timelines, and where things are slipping or bunching up. Other common examples this would unlock: Estimated Close Date vs Actual Close Date Contract Start Date vs Renewal Date Planned Launch Date vs Actual Launch Date Right now, the only workaround is to: Build separate reports for each date property, or Use goals/reference lines or Compare-by (which doesn’t truly solve the “two different date properties” problem) These workarounds don’t give a single, clean, side-by-side visualization of two date fields over time. Requested enhancement: In the custom report builder (and ideally also in single-object reports): Allow multiple date properties on a time-based chart by: Keeping one date property on the X-axis, and Allowing an additional “Date series” or “Compare date properties” slot which lets us plot counts/values by other date properties on the same continuous time axis. Each date property added would appear as its own line/series (with its own color) for the chosen time grain (day/week/month/quarter/year). The chart configuration should let us: Choose the aggregation (e.g., count of records, sum of amount, etc.) per date series Group the X-axis by month, quarter, or year (or use Date part/Frequency as today) Why this matters: Makes it much easier to understand schedule risk and slippage at a portfolio level Reduces the need for multiple reports/exports and external tools just to compare date-based milestones Aligns with how many teams think about project, onboarding, and sales timelines (planned vs forecasted vs actual) Success criteria: I can build a single line chart where: X-axis = month-year Y-axis = count of records Series A = Target Go Live Date Series B = Expected Go Live Date Both series render on the same chart without needing to duplicate datasets or hack around with goals, and can be filtered like any other field in the custom report builder.
...read more