Forum Discussion
Cumulative Backlog Calculation Issue
- 1 year ago
Hi rahberrizvi110 ,
Thanks for your follow-up and clarification.
To address the requirement of bifurcating the backlog issues by previous months in the tooltip, I reproduced the scenario using the same sample structure as before and added a disconnected helper table to group the CreatedDate into month buckets.
Then, using a tooltip page and a measure that calculates how many of those earlier tickets were still unresolved at the start of the selected (hovered) month, I was able to get the expected breakdown.
For example, when hovering over July 2025, the tooltip now displays:
Measure used:
BacklogCountByCreatedMonth = VAR HoveredDate = SELECTEDVALUE('Date'[Date]) VAR HoveredMonthStart = DATE(YEAR(HoveredDate), MONTH(HoveredDate), 1) VAR CurrentCreatedMonth = SELECTEDVALUE('CreatedMonth'[CreatedMonthStart]) RETURN IF ( NOT ISBLANK(HoveredMonthStart) && NOT ISBLANK(CurrentCreatedMonth), CALCULATE ( COUNTROWS (IncidentTable), FILTER ( ALL (IncidentTable), -- Belongs to this Created Month DATE(YEAR(IncidentTable[CreatedDate]), MONTH(IncidentTable[CreatedDate]), 1) = CurrentCreatedMonth && -- Still unresolved at start of hovered month IncidentTable[CreatedDate] < HoveredMonthStart && ( ISBLANK(IncidentTable[ResolvedDate]) || IncidentTable[ResolvedDate] >= HoveredMonthStart ) ) ) )This matches the intent of tracking how many unresolved tickets from earlier months (created in May and June) are still active at the beginning of July.
Please let us know if this aligns with your intended outcome or if you would like to take a different approach for tooltip design.
Hope this helps. Please reach out for further assistance.
Thank you.
Thanks for your response v-veshwara-msft . Could we bifurcate the issues by previous months? Ex- If we hover July then it should show total tickets in July which includes 3 Backlogs from May and 5 Backlogs from June. I need this for Tooltips page.
I appreciate your response.
Hi rahberrizvi110 ,
Thanks for your follow-up and clarification.
To address the requirement of bifurcating the backlog issues by previous months in the tooltip, I reproduced the scenario using the same sample structure as before and added a disconnected helper table to group the CreatedDate into month buckets.
Then, using a tooltip page and a measure that calculates how many of those earlier tickets were still unresolved at the start of the selected (hovered) month, I was able to get the expected breakdown.
For example, when hovering over July 2025, the tooltip now displays:
Measure used:
BacklogCountByCreatedMonth =
VAR HoveredDate = SELECTEDVALUE('Date'[Date])
VAR HoveredMonthStart = DATE(YEAR(HoveredDate), MONTH(HoveredDate), 1)
VAR CurrentCreatedMonth = SELECTEDVALUE('CreatedMonth'[CreatedMonthStart])
RETURN
IF (
NOT ISBLANK(HoveredMonthStart) && NOT ISBLANK(CurrentCreatedMonth),
CALCULATE (
COUNTROWS (IncidentTable),
FILTER (
ALL (IncidentTable),
-- Belongs to this Created Month
DATE(YEAR(IncidentTable[CreatedDate]), MONTH(IncidentTable[CreatedDate]), 1) = CurrentCreatedMonth &&
-- Still unresolved at start of hovered month
IncidentTable[CreatedDate] < HoveredMonthStart &&
(
ISBLANK(IncidentTable[ResolvedDate]) ||
IncidentTable[ResolvedDate] >= HoveredMonthStart
)
)
)
)
This matches the intent of tracking how many unresolved tickets from earlier months (created in May and June) are still active at the beginning of July.
Please let us know if this aligns with your intended outcome or if you would like to take a different approach for tooltip design.
Hope this helps. Please reach out for further assistance.
Thank you.
- v-veshwara-msft1 year ago
Community Support
Hi rahberrizvi110 ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.