Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
3 years ago
Solved

PowerBi Azure DevOps OData WorkItem hierarchy

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 s...
Need Help
  • ibarrau's avatar
    ibarrau
    3 years ago

    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

ibarrau's avatar
ibarrau
Super User
3 years ago

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