March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hello everyone,
I am trying to create a Power BI Desktop report that conveniently shows workitems from our Azure DevOps board. I only want to show workitems that are either Epics, Features or User Stories. Because each Epic can have multiple child Features and each Feature can in turn have multiple child User Stories, I also want to show which workitems are related so we can track the progression of completed child woritem per parent workitem.
In order to visualize this, I extract the WorkItems table from our ADO environment using ODATA. I made sure that the ODATA query only returns the WorkItems that are relevant for me and my team. For now I would like my report to show two things:
I have already created two pages: Overview and WorkItems. In order to show which workitems are related to eachother based on ParentWorkItemId on the WorkItems page, I created 3 additional tables: Epics, Features and Stories. Screenshots of the pages and datamodel are included below. I would like to be able to let users of the report make a selection on the Overview page and drill through to the WorkItems page to show the selected workitems and their related parent/child workitems based on the selected workitem type (Epic/Feature/User Story). However, when I try to do this I encounter a problem because the WorkItems table can only have a single active relationship with either the Epics, Features or Stories table at a time.
Now I figured that using DAX functions like USERELATIONSHIP or RELATED might solve my problem, but I haven't been able to make it work yet. I thought about creating 3 seperate pages (1 for each workitem type) in combination with duplicating each of the workitem tables and creating a single active relationship, but that doesn't seem like an ideal solution.
I am wondering if there is a way to drill through to a page, but take into account the selected workitem type and show results on the WorkItems page by activating one of the inactive relationships (to the Epics table when workitemtype = Epic, to the Features table when workitemtype = Feature etc.). I have included screenshots of a sample report, the relationship view and the desired results below. Any and all advice is welcome. Thank you in advance.
With kind regards,
CorDen.
Overview page
WorkItems page
Model view
Example of desired result: use Epic relationship
Example of desired result: use Feature relationship
Solved! Go to Solution.
@CorDen , In this case, userelationship will not work. You have inactive join because of multiple path
You can keep "workitem" independent/disconnected table
How to filter the slicer of a disconnected table: https://youtu.be/cV5WfaQt6C8
@CorDen , In this case, userelationship will not work. You have inactive join because of multiple path
You can keep "workitem" independent/disconnected table
How to filter the slicer of a disconnected table: https://youtu.be/cV5WfaQt6C8
Hi @amitchandak, thanks a lot for your response and suggested solution. I managed to get the desired result by making the following DAX formula, applying it to the table visuals and filtering on isnotblank:
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
134 | |
91 | |
89 | |
64 | |
58 |
User | Count |
---|---|
201 | |
137 | |
107 | |
72 | |
68 |