Hello guys,
I'm facing an interesting problem.
Basically, I created some measures to calculate if a Purchase order (PO) has been received on time or not. To do this, the measure ( datediff) calculates the difference in days between the expected date (ETA) and the effective receipt date.
Nevertheless, each PO contains different products and each of them can be received at different time. In some case a PO can received a part of the product on time and the other part with a delay. In this case I would like to count this PO as delayed.
To prevent this situation the datediff function will always calculate the difference between the minimum expected date and the maximum receipt date as you can see below :
Date Diff =
DATEDIFF(MIN('Order'[expected receipt date]),LASTDATE('Receipt table'[Receipt Date]),DAY)
To calculate if a PO has been received on time :
PO on Time = CALCULATE([Count Distinct PO],
FILTER('Receipt table',([Date Diff]<15)),
FILTER('Receipt table',([Date Diff]>=-14)))
To calculate if a PO has been received with a delay :
PO delayed = CALCULATE([Count Distinct PO],
FILTER('Orders ',([Date Diff]>=15)))
This works perfectly when there is no aggregation as you can see below ( it's one PO with 3 products) :
But when I "aggregate" the data by PO, there is an issue as you can see below. The PO is counted as on time and delayed at the same time whereas it should be count only as delayed.
The behavior of the date diff function is good because it takes the highest diff in days (16), nevertheless, the PO on time doesn't react has expected because it counts the PO as on time whereas the datediff result is 16 and the function is setup to count as on time only if the date is <15 and >=-14.
I get the impression that the aggregation I have done is implicit through the table and I should explicitly aggregate the data in my measure. Therefore my questions are :
- Why my PO on time function does't take the result 16 to avoid to count it as a PO on time ?
- What do you recommend to fix the issu and group by the datediff result by PO ?
Many thanks for your help,
Hi @ilyasss ,
- Why my PO on time function does't take the result 16 to avoid to count it as a PO on time ?
In the above table visual, [Date Diff (ETA, Receipt date)] is calculated based on the minimum ETA and the maximum Receipt date of the designated Purchase order. So, [Date Diff (ETA, Receipt date)] = 16 is not the result of the last row of records in your table visual.
And for total values of [PO on time] and [PO delayed] are calculated based on the distincted count of Purchase order.
I create a simple example based on the data you provided to explain clearly:
- What do you recommend to fix the issu and group by the datediff result by PO ?
Try to create another two measures based on your measures.
PO on time 2 = IF([PO on Time]=1&&[PO delayed]=BLANK(),1)PO delayed 2 = IF([PO delayed]=1,1)
BTW, .pbix file attached.
Best Regards,
Icey
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello @Icey ,
Thank you for your very detailed explaination which helped a lot to understand the logic.
Nevertheless, the solution proposed doesn't fit because both of the POs should be delayed and with the solution there is only one.
Finally I created a summarize table to group by the Purchase order by date diff and use this date to make the calculcation and as you can see below, now both of the Po are counted as delayed and zero on time :
Many thanks for your help,
Helpful resources
Microsoft Fabric Learn Together
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Power BI Monthly Update - April 2024
Check out the April 2024 Power BI update to learn about new features.
Fabric Community Update - April 2024
Find out what's new and trending in the Fabric Community.
