Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Hi Nate,
Here's a sample of my query. Each row represents a PO created in 2019. The milestones occur along the way from it's preceding RFQ creation and approval through PO creation to receipt to delivery. I'd like my visualization to gather up all POs for a given quarter, average out the time spent at each phase and produce a horizontal stacked bar with 4 segments representing the following:
RFQ Creation - RFQ Aproval (days required)
RFQ Approval - PO Fiscal Effective Date (days required)
PO Fiscal Effective - PO Receipt (days required)
PO Receipt - PO Delivery (days required)
Thanks and Regards,
Rob
Hi Nate,
Which text are you referring to? All I've done so far is merge the tables using Excel Power Query and removed all the non-relevant columns for the sake of displaying here.
Rob
Sorry, I mean the text from Excel, instead of a screenshot. Then I can copy and paste that as a source in Power BI.
Nate,
Here you go. I've never posted an entire table before so let me know if it's not what you're after. Below is the first 30 rows of the table.
PO_NUMBERRFQ.CREATED_DATERFQ.APPROVED_DATEFISCAL_EFFECTIVE_DATELAST_RECEIPT_DATELAST_DELIVERY_DATE
| 1118979 | 12/20/2018 | 12/28/2018 | 1/1/2019 | 2/26/2019 | 3/24/2019 |
| 1118980 | 12/31/2018 | 12/31/2018 | 1/1/2019 | 1/16/2019 | 1/26/2019 |
| 1118989 | 12/31/2018 | 1/1/2019 | 1/1/2019 | 1/9/2019 | 1/19/2019 |
| 1119003 | 11/19/2018 | 1/2/2019 | 1/2/2019 | 1/23/2019 | 2/20/2019 |
| 1118878 | 12/12/2018 | 12/20/2018 | 1/2/2019 | 3/28/2019 | 6/17/2019 |
| 1118877 | 12/19/2018 | 12/19/2018 | 1/2/2019 | 1/17/2019 | 1/30/2019 |
| 1118990 | 12/26/2018 | 1/1/2019 | 1/2/2019 | 4/10/2019 | 4/28/2019 |
| 1118996 | 12/26/2018 | 12/31/2018 | 1/2/2019 | 2/14/2019 | 2/23/2019 |
| 1118997 | 1/2/2019 | 1/2/2019 | 1/2/2019 | 1/10/2019 | 1/16/2019 |
| 1119025 | 4/3/2018 | 12/30/2018 | 1/3/2019 | 1/29/2019 | 2/26/2019 |
| 1119012 | 10/4/2018 | 1/2/2019 | 1/3/2019 | 5/21/2019 | 5/21/2019 |
| 1119005 | 11/14/2018 | 1/2/2019 | 1/3/2019 | 4/1/2019 | 4/30/2019 |
| 1119022 | 12/17/2018 | 1/1/2019 | 1/3/2019 | 2/25/2019 | 10/9/2019 |
| 1119013 | 12/19/2018 | 1/2/2019 | 1/3/2019 | 1/22/2019 | 3/6/2019 |
| 1119014 | 12/20/2018 | 2/18/2019 | 1/3/2019 | ||
| 1119021 | 12/21/2018 | 1/1/2019 | 1/3/2019 | 1/18/2019 | 1/20/2019 |
| 1119029 | 12/24/2018 | 1/2/2019 | 1/3/2019 | 1/9/2019 | 1/15/2019 |
| 1119024 | 12/24/2018 | 1/2/2019 | 1/3/2019 | 1/11/2019 | 1/15/2019 |
| 1119030 | 12/24/2018 | 1/2/2019 | 1/3/2019 | 1/10/2019 | 1/16/2019 |
| 1119010 | 12/26/2018 | 1/2/2019 | 1/3/2019 | 1/9/2019 | 1/16/2019 |
| 1119023 | 12/28/2018 | 1/1/2019 | 1/3/2019 | 1/18/2019 | 1/20/2019 |
| 1118992 | 12/31/2018 | 1/2/2019 | 1/3/2019 | 1/31/2019 | 2/19/2019 |
| 1119006 | 12/31/2018 | 1/2/2019 | 1/3/2019 | 2/7/2019 | 2/21/2019 |
| 1119006 | 12/31/2018 | 1/2/2019 | 1/3/2019 | 2/7/2019 | 2/21/2019 |
| 1119028 | 12/31/2018 | 1/1/2019 | 1/3/2019 | 1/14/2019 | 1/23/2019 |
| 1119027 | 12/31/2018 | 1/1/2019 | 1/3/2019 | 1/10/2019 | 1/23/2019 |
| 1119027 | 12/31/2018 | 1/1/2019 | 1/3/2019 | 1/10/2019 | 1/23/2019 |
| 1119027 | 12/31/2018 | 1/1/2019 | 1/3/2019 | 1/10/2019 | 1/23/2019 |
| 1119019 | 12/31/2018 | 1/3/2019 | 1/3/2019 | 1/9/2019 | 1/28/2019 |
@Anonymous5 - You could use something like the attached pbix file. There are several steps to consider with this solution:
Note: The parameters table could be eliminated and the measures simplified, if only a single type of analysis makes sense.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 22 | |
| 20 | |
| 14 | |
| 13 | |
| 13 |
| User | Count |
|---|---|
| 62 | |
| 40 | |
| 39 | |
| 39 | |
| 38 |