Data Modeling - Parent Child

[ElvirBotic]

I am curious on how I should approach an issue I am facing. I have a data source that collects data at two different granularities. One is a "parent" record that highlights total budget. In the same table I have a column that you can enter if it has a parent budget. So, in one source I have data for "child" records that allows users to enter in if it is related to a "parent" budget. My challenege is do I leave in the parent records and when building measures include filter context to exclude the parent record? or do I create a sepearte table for parent records? and force a physical relationship of 1:*? 

With that how do I overcome ambiguity? Here is what I mean. I have a table that captures all comments and they're written to a different dat source. If I create a seperate table for parent and one for child it would create ambiguity between all three tables and I am unsure of how I can cirumvent that. I don't think it would be good to bloat the model by creating another table to filter to only parent comments and one for child comments. I hope that makes sense. 

[rajendraongole1 · Accepted solution]

Hi @ElvirBotic -you need to carefully consider how to model and filter data to avoid complexity while maintaining flexibility in analysis. you avoid the need to manage multiple tables and complex relationships.Flexible Filtering: You can easily filter out parent records in specific measures without complicating the data model.Fewer Relationships: This approach eliminates the need for creating additional relationships between separate tables, reducing the risk of relationship ambiguity.

reference solved threads FYR:

Solved: Parent-Child hiearchy handling with multiple Paren... - Microsoft Fabric Community

Data Modeling - Parent Child - Microsoft Fabric Community

Solved: Multi Level Parent Child Hierarchy - Microsoft Fabric Community

Display Child records if associated to a Parent in... - Microsoft Fabric Community