Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hi guys,
Been tinkering around with Azure Devops and PowerBi through OData lately and stumbled upon the same problem multiple of times.
Completely understand the OData queries and all but can't seem to find a logical way to create a hierarchy in the powerbi model.
Options I've tried:
Retrieve Epics, Features and User Stories on three seperate occasions and put them into three seperate tables and create relations between them. Problem: When Area, Boardlocation, Users and Iterations are also retrieved only one of the three (epic, feature, user story) can have a relation to them.
Options I've looked into but didn't seem to be a solution:
Retrieving WorkItemLink (SourceWorkItemId & TargetWorkItemId) and trying to make a relation but does not activate because of a loop.
Does anyone have any experience with this? I'd be glad to know. Cheers!
Current layout:
Solved! Go to Solution.
Hi. Regarding data modeling I would build a single dimension for User Stories with minimun and necessary columns with left join for features and epics. It's like classic scenario of Product, Product SubCategory and Product Category of adventure works. The maximum granularity is stories. So take it al repeated and redundant in there. A Story dimension will have all categorical story values + feature name + epic name. You can also take other columns that will help you relate with tables like userid.
That would be the way to model that.
I hope that make sense
Happy to help!
Hi. Regarding data modeling I would build a single dimension for User Stories with minimun and necessary columns with left join for features and epics. It's like classic scenario of Product, Product SubCategory and Product Category of adventure works. The maximum granularity is stories. So take it al repeated and redundant in there. A Story dimension will have all categorical story values + feature name + epic name. You can also take other columns that will help you relate with tables like userid.
That would be the way to model that.
I hope that make sense
Happy to help!
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.