Forum Discussion
Drill-Through Report with Different Tables
bellabelbel Hey,
- Use a shared Work Item dimension for drill‑through (not fields from separate fact tables). Create a DimWorkItem with Id, ParentId, WorkItemType, Title, State, etc. Relate Fact Work Items[WorkItemId] → DimWorkItem[Id] and Gather Documentation[WorkItemId] → DimWorkItem[Id]. Set the drill‑through field to DimWorkItem[Id] (or a surrogate key from this dimension). This ensures the drill context flows to both pages/tables.
- Drive hierarchy on the drill‑through page from that dimension. Add hierarchy logic in DimWorkItem (Path = PATH(Id, ParentId); EpicId = VALUE(PATHITEM(Path, PATHLENGTH(Path)))). Build your table visual from DimWorkItem and filter rows where [EpicId] equals the drilled value (e.g., a simple measure: ShowUnderSelectedEpic = IF(MIN(DimWorkItem[EpicId]) = SELECTEDVALUE(DimWorkItem[Id]), 1, 0) and set visual filter = 1). This will list Features, User Stories, and Tasks under the selected Epic.
Thanks
Haish K
If I resolve your issue. Kindly give kudos to this post and accept it as a solution so other can refer this.
For reference, here is my model and the relationship I've established between the two tables:
Here is my summary and drilled through page and the associated tables I've used for them. Despite removing Keep All Filter, I'm still only seeing Epic level in my drill through page:
Hello Again bellabelbel ,
Thank you for providing the detailed screenshots and explaining the requirement. After reviewing them, I can confirm that your data model and relationships are correctly set up, and the behavior you’re seeing is expected. In Power BI, drill through only passes the filter context from the table used in the source visual. Although Fact Work Items and GatherDocumentation Expanded are linked by Work Item Id, drill through doesn’t use that relationship to rebuild row-level or hierarchical context in another fact table. Since your summary page is based on Fact Work Items, only the Epic level can consistently be passed through, while Feature, User Story, and Task are not included when the target page uses a different table.
Changing relationship directions, toggling Keep all filters, or using measures doesn’t affect this outcome. These options impact how visuals filter data but don’t change how drill through transfers context. To show the full hierarchy under a selected Epic on the drill through page, both source and target pages need to use the same table or a shared work item dimension containing Epic, Feature, User Story, and Task in the same row context. With separate tables on each page, drill through will only return the Epic level, and there’s no additional configuration to change this behavior.
Thank you.Hi bellabelbel ,
I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.
Thank you.Hi bellabelbel ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
- HarishKM
Super User
bellabelbel Hey,
- Use a shared Work Item dimension for drill‑through (not fields from separate fact tables). Create a DimWorkItem with Id, ParentId, WorkItemType, Title, State, etc. Relate Fact Work Items[WorkItemId] → DimWorkItem[Id] and Gather Documentation[WorkItemId] → DimWorkItem[Id]. Set the drill‑through field to DimWorkItem[Id] (or a surrogate key from this dimension). This ensures the drill context flows to both pages/tables.
- Drive hierarchy on the drill‑through page from that dimension. Add hierarchy logic in DimWorkItem (Path = PATH(Id, ParentId); EpicId = VALUE(PATHITEM(Path, PATHLENGTH(Path)))). Build your table visual from DimWorkItem and filter rows where [EpicId] equals the drilled value (e.g., a simple measure: ShowUnderSelectedEpic = IF(MIN(DimWorkItem[EpicId]) = SELECTEDVALUE(DimWorkItem[Id]), 1, 0) and set visual filter = 1). This will list Features, User Stories, and Tasks under the selected Epic.
Thanks
Haish K
If I resolve your issue. Kindly give kudos to this post and accept it as a solution so other can refer this.