This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Alright boys, girls, and malfunctioning automata, I have a conudrum that I would like some assistance resolving.
In image 1, is the table in my dashboard that honestly needs some work.
What I would like to do is add a seperater column inbetween each COLO that simply states the COLO that is to follow. Or some way to break each COLO into sections within the table so their is a visual break in the data.
The data the table uses itself is fairly simple:
| COLO 1 | L1 Cx Start | 12/19/2024 | 12/23/2024 | 2 |
| COLO 1 | L1 Cx Finish | 2/26/2025 | 1/31/2025 | -18 |
| COLO 1 | L2 CX Start | 2/27/2025 | 1/31/2025 | -19 |
| COLO 1 | L2 Cx Finish | 5/7/2025 | 4/17/2025 | -14 |
| COLO 1 | L3 Cx Start | 5/8/2025 | 4/18/2025 | -14 |
| COLO 1 | L3 Cx Finish | 7/3/2025 | 6/13/2025 | -14 |
| COLO 1 | L4 Cx Start | 7/5/2025 | 6/14/2025 | -17 |
| COLO 1 | L4 Cx Finish | 8/4/2025 | 7/15/2025 | -17 |
| COLO 1 | L5 Cx Start | 8/5/2025 | 7/18/2025 | -15 |
| COLO 1 | L5 Cx Finish | 8/6/2025 | 7/19/2025 | -15 |
| COLO 2 | L1 Cx Start | 2/10/2025 | 1/9/2025 | -22 |
| COLO 2 | L1 Cx Finish | 2/28/2025 | 1/29/2025 | -22 |
| COLO 2 | L2 CX Start | 4/17/2025 | 4/2/2025 | -11 |
| COLO 2 | L2 Cx Finish | 6/27/2025 | 6/13/2025 | -10 |
| COLO 2 | L3 Cx Start | 6/30/2025 | 6/16/2025 | -10 |
| COLO 2 | L3 Cx Finish | 8/18/2025 | 8/4/2025 | -10 |
| COLO 2 | L4 Cx Start | 8/19/2025 | 8/5/2025 | -12 |
| COLO 2 | L4 Cx Finish | 9/13/2025 | 8/29/2025 | -12 |
| COLO 2 | L5 Cx Start | 9/13/2025 | 8/30/2025 | -11 |
| COLO 2 | L5 Cx Finish | 9/15/2025 | 9/2/2025 | -11 |
| COLO 3 | L1 Cx Start | 3/12/2025 | 4/1/2025 | 14 |
| COLO 3 | L1 Cx Finish | 5/20/2025 | 5/1/2025 | -14 |
| COLO 3 | L2 CX Start | 6/5/2025 | 5/23/2025 | -8 |
| COLO 3 | L2 Cx Finish | 8/21/2025 | 8/11/2025 | -8 |
| COLO 3 | L3 Cx Start | 8/22/2025 | 8/12/2025 | -8 |
| COLO 3 | L3 Cx Finish | 10/10/2025 | 9/30/2025 | -8 |
| COLO 3 | L4 Cx Start | 10/11/2025 | 10/1/2025 | -9 |
| COLO 3 | L4 Cx Finish | 11/6/2025 | 10/27/2025 | -9 |
| COLO 3 | L5 Cx Start | 11/7/2025 | 10/28/2025 | -9 |
| COLO 3 | L5 Cx Finish | 11/8/2025 | 10/29/2025 | -9 |
| COLO 4 | L1 Cx Start | 4/2/2025 | 7/7/2025 | 66 |
| COLO 4 | L1 Cx Finish | 7/3/2025 | 7/7/2025 | 1 |
| COLO 4 | L2 CX Start | 7/15/2025 | 7/8/2025 | -5 |
| COLO 4 | L2 Cx Finish | 10/6/2025 | 9/29/2025 | -5 |
| COLO 4 | L3 Cx Start | 10/8/2025 | 10/1/2025 | -5 |
| COLO 4 | L3 Cx Finish | 11/25/2025 | 11/18/2025 | -5 |
| COLO 4 | L4 Cx Start | 11/26/2025 | 11/19/2025 | -6 |
| COLO 4 | L4 Cx Finish | 12/23/2025 | 12/16/2025 | -5 |
| COLO 4 | L5 Cx Start | 12/24/2025 | 12/17/2025 | -6 |
| COLO 4 | L5 Cx Finish | 12/26/2025 | 12/18/2025 | -6 |
| COLO 5 | L1 Cx Start | 4/16/2025 | 8/12/2025 | 82 |
| COLO 5 | L1 Cx Finish | 8/27/2025 | 7/17/2025 | -30 |
| COLO 5 | L2 CX Start | 9/10/2025 | 9/9/2025 | -1 |
| COLO 5 | L2 Cx Finish | 11/25/2025 | 11/24/2025 | -1 |
| COLO 5 | L3 Cx Start | 11/26/2025 | 11/26/2025 | 0 |
| COLO 5 | L3 Cx Finish | 1/16/2026 | 1/16/2026 | 0 |
| COLO 5 | L4 Cx Start | 1/17/2026 | 1/17/2026 | 0 |
| COLO 5 | L4 Cx Finish | 2/11/2026 | 2/11/2026 | 0 |
| COLO 5 | L5 Cx Start | 2/12/2026 | 2/12/2026 | 0 |
| COLO 5 | L5 Cx Finish | 2/13/2026 | 2/13/2026 | 0 |
What I'm looking for is something similiar to the excel table below but with the L1 and L2s called out like in the example up top.
Have you considered using paginated reports for this?
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.