Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hello! I have this Issue where my fact table has a ClientID, their Balances, a "Kind" and a Branch.
We have the concept of Regions and of course we would like to filter on them.
The thing is, for some Kind of clients, the Region is based on it's Branch. And for the other Kind, it's a direct list by clientID.
So I guess my question is if we can have a dimension come from two different dimTables, one for some records on some condition, and another for the other records on other condition.
I don't know how to call this scenario. Partial dimensions? Complex dimentions? Partitioned? Composite? I hope I'm being clear.
Thank you for your help.
Hi @El_Servas
It depends on how you want to create visuals in the report. If you are going to display two kinds of clients data in different visuals, it's ok to have two dimension tables in the model. Both dimension tables are connected to the fact table and filter the fact table separately.
If you want to have both kinds of clients in the same dimension table, for the kind whose Region is not based on Branch, does it mean that its "Branch" data is null? If so, you can replace null in Branch with its clientID. That is to treat "ClientID" as "Branch" or treat "ClientID" as "Region". Is this acceptable?
Best Regards,
Community Support Team _ Jing
If this post helps, please Accept it as Solution to help other members find it.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.