The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hi, @jaime_blackwell , based on your description, I think the order of evalution in CALCULATE matters.
CALCULATE(<expression>[, <filter1> [, <filter2> [, …]]])
filters evaluate parallelly, which means, in your case, FILTER( AllPPMTickets , AllPPMTickets[Resolved_status] = TRUE ) doesn't get affected by USERELATIONSHIP(AllPPMTickets[Resolved_date_time], Dates[Date] ); it evaluates under the former active relationship.
You may try this measure,
[ Tickets_Resolved ] =
CALCULATE (
COUNTX ( AllPPMTickets, AllPPMTickets[Ticket_id] ),
CALCULATETABLE (
FILTER ( AllPPMTickets, AllPPMTickets[Resolved_status] = TRUE ),
USERELATIONSHIP ( AllPPMTickets[Resolved_date_time], Dates[Date] )
)
)
Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension! |
DAX is simple, but NOT EASY! |
Hi @CNENFRNL ,
Thanks so much for that suggestion, however the values produced by the measure you provided are the same. I figured that the order of the filter and userelationship functions would be irrelevant because the relationship does not affect the filtered column, so the result should be the same either way.
The measure is basically behaving as though the USERELATIONSHIP() function isn't working at all.
Update: I was able to resolve the issue using the below
[ Tickets_Resolved ] =
VAR
PPMTickets = CALCULATETABLE (
FILTER ( AllPPMTickets, AllPPMTickets[Resolved_status] = TRUE ),
USERELATIONSHIP ( AllPPMTickets[Resolved_date_time], Dates[Date] )
)
RETURN
COUNTROWS( PPMTickets )
Thank you again for your help!
User | Count |
---|---|
28 | |
12 | |
8 | |
7 | |
5 |
User | Count |
---|---|
36 | |
14 | |
12 | |
7 | |
7 |