Relationship issue - Fact and DIM

BharathS1307 

Fix your original DIM tables - remove nulls/duplicates in Power Query

Connect each DIM (1) to all 5 FACTs (many) using the natural key columns. 

Slicers on DIM tables work across all facts automatically.

Keep dims separate, clean, unique.

Hi BharathS1307 ,

1.Clear dimension table in power query: Remove nulls and duplicates
2. Handle nulls in fact tables.
3. Use one to many relationship from dim to fact (cross filter single and relationship active)

Your 2nd and 3rd approach seems ambigous and filtering may not propagate correctly

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!

If a slicer from a dimension shows (Blank) or gives inconsistent filtering across multiple fact tables, the most common causes are:

• keys in the fact table that do not exist in the dimension

• null/blank keys in the fact tables

• many-to-many style behavior introduced by the “master dim” logic