I finally got one right! -slighlty different to yours - but just compared if requireded date = shipped date Var Ordertable =SUMMARIZE( Orders,Orders[RequiredDate],Orders[ShippedDate], "On Time",[RequiredDate]=[ShippedDate]) Return countrows(filter(Ordertable,[On Time]))
oooh, having a bad streak all due to my lack of attention to detail... Forgot to check the glossary for the meaning of "on time orders" this time... ... ok, time to regroup and get my groove back! 💪
Thanks for the video. Feedback - DAX Query ( evaluate.) within power bi, in my opinion is similar to writing a SQL statement. I see the majority of ppl using power query, then filter on normal table to get the answer.
For these different questions, can you also suggest a simpler solution that the one that tries to reproduce a visual table with the "SUMMARIZE" function ? Example for this one, a simple COUNTROWS and a FILTER Ship date = Request date
@@CurbalEN yes- this is my business- we want nothing too early- when something arrives we have 60 days to pay. We want everything just in time. (Which is a PITA!)
I finally got one right! -slighlty different to yours - but just compared if requireded date = shipped date
Var Ordertable
=SUMMARIZE(
Orders,Orders[RequiredDate],Orders[ShippedDate],
"On Time",[RequiredDate]=[ShippedDate])
Return
countrows(filter(Ordertable,[On Time]))
🥳🥳🥳 It is only going to get better and better!
oooh, having a bad streak all due to my lack of attention to detail... Forgot to check the glossary for the meaning of "on time orders" this time...
... ok, time to regroup and get my groove back! 💪
You can do this!!
meetoo :o)
On no! :(
Thanks for the video. Feedback - DAX Query ( evaluate.) within power bi, in my opinion is similar to writing a SQL statement. I see the majority of ppl using power query, then filter on normal table to get the answer.
For these different questions, can you also suggest a simpler solution that the one that tries to reproduce a visual table with the "SUMMARIZE" function ?
Example for this one, a simple COUNTROWS and a FILTER Ship date = Request date
I am just trying to show a method that works very often for those that struggle with DAX. Hope it makes sense
Can we use a strict equal (==) and get the desired result ?
It seems that if shipped before, it should also be on time because it is not late.
Too early is not good either in certain businesses
anyway, it was described on the glossary :P
@@CurbalEN yes- this is my business- we want nothing too early- when something arrives we have 60 days to pay. We want everything just in time. (Which is a PITA!)
@CurbalEN understood thank you for the feedback. Keep up the fantastic work
Hello! Is it the same to use calculatetable instead of filter?
No, they are different!
Interpreting the question is malware 😂
I saw "Orders delivered on the day requested" as Orders delivered on the day they are ordered🤦
😂😂😂 sorrry!!
Oh, it is only with orders shipped on the same day.
I also counted the orders shipped before the requested date 🥲
me too ...
Too early can be problematic also!
and it was there, black on white. snif snif
😥