Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hi All,
I'm new to powerbi. I want to create the historical plot of no. of overdue document.
Currenly, i can count Today overdue case by using Today() function in powerquery.
In the sample below, i can count no. of overdue cases = 2 cases.
Today Status | |
NextReview | Overdue Flag |
15-Oct-20 | No |
15-May-20 | No |
15-Jan-21 | No |
15-Dec-20 | No |
15-Mar-20 | Yes |
11-Mar-20 | Yes |
However, with this methold i cannot see historical trend of overdue cases. What i want to achieve is something like this.
Overdue Status as at | |||||||
Deadline | 24/02/20 | 02/03/20 | 09/03/20 | 16/03/20 | 23/03/20 | 30/03/20 | 06/04/20 |
25-Feb-20 | Not Overdue | Overdue | Overdue | Overdue | Overdue | Overdue | Overdue |
27-Feb-20 | Not Overdue | Overdue | Overdue | Overdue | Overdue | Overdue | Overdue |
01-Mar-20 | Not Overdue | Overdue | Overdue | Overdue | Overdue | Overdue | Overdue |
26-Feb-20 | Not Overdue | Overdue | Overdue | Overdue | Overdue | Overdue | Overdue |
31-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue |
29-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
29-Apr-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue |
17-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
25-Feb-20 | Not Overdue | Overdue | Overdue | Overdue | Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
25-Feb-20 | Not Overdue | Overdue | Overdue | Overdue | Overdue | Overdue | Overdue |
25-Feb-20 | Not Overdue | Overdue | Overdue | Overdue | Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
27-Mar-20 | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Not Overdue | Overdue | Overdue |
This is the final result that i want to see but i don't want to create calculate column to flag the status of everyday date i want to count the overdue case.
Date | No. of Overdue Case |
24/02/20 | 0 |
02/03/20 | 7 |
09/03/20 | 7 |
16/03/20 | 7 |
23/03/20 | 8 |
30/03/20 | 18 |
06/04/20 | 19 |
Is there anyway to acheive this ?
Thanks !
Solved! Go to Solution.
@Anonymous
You may refer to the following post.
@Anonymous
You may refer to the following post.
Hello @Anonymous ,
What is the datatable structure?
Cheers!
Vivek
https://www.vivran.in/
Connect on LinkedIn
Hi @vivran22 ,
I am the authur's colleague.
Our full data structure look like this.
We simplify the data in the question above. Our main forcus is the table on the left (Appinfo_Incoming).
User | Count |
---|---|
122 | |
69 | |
67 | |
58 | |
52 |
User | Count |
---|---|
187 | |
94 | |
67 | |
63 | |
54 |