Data Modeling

[VK-Vishnu]

Hi, am working in one migration project , i face issue is existing report under 4 sub reports now i migrate that report to bi and craete single reoprt, the issue is i had 4 fact tables and 4 dim tables, dim tables are sharing fact table like example fact1 connect with dim1,2,3 and fact 2 connect dim 2,3,4. now i want to moddeling everything under a single schema. how its modeling ?

[VK-Vishnu]

I already tried this ways but its not working , i have 3 fact and 4 dim, fact 1 connect wit dim 1,2,3,4 then fact 2 connect with dim 1,3,4 and fact 3 connect with dim 2,3,4. move visula side 1st page having only 7 sliceers that slicers are comman and 2nd page having many visulas and also having some slicers, and also i want both slicers have intract in visuals and main condition fom my clint side is desighn model on star schema. what i doo

[v-sshirivolu · Accepted solution]

Hi @VK-Vishnu ,

If you have already implemented a star schema and the common slicers are still not filtering all visuals correctly, then the issue may be related to the relationship configuration rather than the schema design itself. In a star schema, shared dimension tables should filter all connected fact tables through active one-to-many relationships.

Could you please share a screenshot or diagram of your current data model, including the relationships between the 3 fact tables and 4 dimension tables? Also, please confirm whether the slicers are built from dimension tables and whether all relationships are active.
This will help identify whether the issue is related to relationship paths, filter propagation, or model design.

[v-sshirivolu]

Hi @VK-Vishnu ,

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. 

[v-sshirivolu]

Hi @VK-Vishnu ,
Thanks for reaching out to Fabric Community Forum.

As per Microsoft Power BI guidance, the recommended approach is to model your data using a star schema, where fact tables store measurements or events, and dimension tables store descriptive attributes used for filtering and grouping. In a star schema, fact tables contain key columns that relate to dimension tables, allowing dimensions to filter and summarize the data stored in facts.

You should connect your fact tables to the relevant dimension tables using one-to-many relationships (dimension - fact). This design provides a structured and intuitive model for reporting and analysis and aligns with Microsoft's recommended approach for Power BI semantic models.

Reference:
https://learn.microsoft.com/en-us/power-bi/guidance/star-schema

Thank you.

[v-sshirivolu]

Hi @VK-Vishnu ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

[Kedar_Pande]

@VK-Vishnu 

Keep your dim tables as single tables. Do not duplicate them. Each fact table connects to the shared dims through individual relationships

Dim1 --- Fact1 --- Dim2
|
Fact2 --- Dim3
|
Dim4

mark only one relationship as active between any two tables, use USERELATIONSHIP in DAX for inactive ones.

[InsightsByV]

Hi,

In your case:

Create a master date table and connect it with the respective tables and ensure that the relationships are correctly defined (one to many) and single direction.

Use columns from this master date table for all your slicers to ensure uniformality across pages.