Burn Down Chart By Due Date with Conditions

[AppleUSN]

I am trying to create a burn down of orders past due which burn on the date that they are planned to ship.  See my attached data and chart.

Part Description	Contract Date	Dock Date
HARNESS ASSEMBLY, ENGINE CONTROL	3/8/2023	4/6/2023
HARNESS ASSEMBLY, ENGINE CONTROL	3/8/2023	4/6/2023
HARNESS ASSEMBLY, ENGINE CONTROL	3/10/2023	5/11/2023
HARNESS ASSEMBLY, ENGINE CONTROL	3/10/2023	5/11/2023
HARNESS ASSEMBLY, ENGINE CONTROL	3/10/2023	5/11/2023
HARNESS ASSEMBLY, ENGINE CONTROL	3/31/2023	6/2/2023
HARNESS ASSEMBLY, ENGINE CONTROL	3/31/2023	6/2/2023
HARNESS ASSEMBLY, ENGINE CONTROL	3/31/2023	6/2/2023
HARNESS ASSEMBLY, ENGINE CONTROL	4/10/2023	4/10/2023
HARNESS ASSEMBLY, ENGINE CONTROL	4/10/2023	4/10/2023

Date (MM/DD)	3/27/23	4/3/23	4/10/23	4/17/23	4/24/23	5/1/23	5/8/23	5/15/23	5/22/23	5/29/23	6/5/23	6/12/23	6/19/23
Actual count of overdue and future overdue	8
Forecast count of overdue lines		6	6	6	6	6	3	3	3	0	0	0	0

[Anonymous]

Hi @AppleUSN,

It seems like you want to analysis the date range that defined by multiple date fields. For this scenario, you can take a look at the Gregs’ blog 'start date' 'end date' part of helps.

Before You Post, Read This 

In addition, you can also try to create a expand table to expand all the detail date records into the ranges to help power accurately map these records.

Solved: Spread revenue across period based on start and en... - Microsoft Power BI Community

Regards,

Xiaoxin Sheng

[AppleUSN]

Hi @Anonymous ,

I actually found a solution to what I was trying to do.  I had to make some tweaks to it as it wasnt showing as I expected.

Planned Delivery =

VAR _count =

    CALCULATE (

        COUNT ( 'PWA OOR'[Past Dues] ),

        FILTER ( ALL( 'Date' ), 'Date'[Date] > MAX( 'Date'[Date] ) ),

        USERELATIONSHIP ( 'Date'[Date], 'PWA OOR'[On Dock Date] )

    ) + 0

VAR _date =

    CALCULATE (

        SELECTEDVALUE ( 'PWA OOR'[On Dock Date] ),

        USERELATIONSHIP ( 'Date'[Date], 'PWA OOR'[On Dock Date] )

    )

RETURN

_count

First, I am still trying to learn the DAX code so I can understand what it is doing on each line.  Sometimes I can see it but sometimes I cannot.  In this case above I had to change MIN to MAX and the RETURN _Count was also different.  It was removing the values before I changed it.  I appreciate you reaching out and giving more blogs to read though.  Most of it I have incorporated already but that was a lot of information in one spot.

[Anonymous]

Hi @AppleUSN,

I'm glad to hear you find the solution and share the expressions here, they should help with other who faced the similar scenarios.
For Dax study, you can also take a look at the following link about learning/train with Dax language:

Use DAX in Power BI Desktop - Training | Microsoft Learn

Regards,

Xiaoxin Sheng