Forum Discussion
Displaying weekly data for last 3 month in Matrix Table
- Anonymous1 year ago
Thanks for the reply from lbendlin and techies .
hasarinfareeth , the following test is for your reference.
Create a measure as follows
Value = VAR _RANGEEND = CALCULATE ( MAX ( 'Date Table'[Date] ), ALL ( 'Date Table' ) ) VAR _RANGESTART = EOMONTH ( _RANGEEND, - 3 ) + 1 RETURN CALCULATE ( COUNT ( 'Closed Tickets'[Ticket Reference] ), FILTER ( 'Closed Tickets', 'Closed Tickets'[Closed On] >= _RANGESTART && 'Closed Tickets'[Closed On] <= _RANGEEND ) )Click "Expand all down one level in the hierarchy".
Output:
If I update the data for February, the effect is as follows:
Best Regards,
Yulia XuIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for the reply from lbendlin and techies .
hasarinfareeth , the following test is for your reference.
Create a measure as follows
Value =
VAR _RANGEEND =
CALCULATE ( MAX ( 'Date Table'[Date] ), ALL ( 'Date Table' ) )
VAR _RANGESTART =
EOMONTH ( _RANGEEND, - 3 ) + 1
RETURN
CALCULATE (
COUNT ( 'Closed Tickets'[Ticket Reference] ),
FILTER (
'Closed Tickets',
'Closed Tickets'[Closed On] >= _RANGESTART
&& 'Closed Tickets'[Closed On] <= _RANGEEND
)
)
Click "Expand all down one level in the hierarchy".
Output:
If I update the data for February, the effect is as follows:
Best Regards,
Yulia Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks a lot Anonymous . This has worked for me but the sorting is not as I expected. I alredy have a sorting based on the total number of tickets per team which is required. With this sorting the month is jumbled and is not as expected. Is there anything I am missing on the sorting?
- Anonymous1 year agoNot applicable
Could you please show a screenshot of the problem you are having? I sorted through the option shown and everything seems to be working fine. Is this what you wanted?
Best Regards,
Yulia Xu