Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hello, I'm new to PowerBI and have some problem with table relationship. The table relationship concept in PowerBI seems different with the one in common DBMS.
Suppose I have these simple tables:
Branch
branchid
branchname
Customer
branchid
cutomerid
customername
SalesPerson
branchid
salespersonid
salespersonname
Transaction
salespersonid
customerid
transactionid
transactiondate
qtysold
Branch table has relation with Customer and SalesPerson table on branchid column,.
Customer table has relation with Transaction table on customerid column
SalesPerson table has relation with Transaction table on salespersonid column
I can only make relationship from Transaction table to either Customer or SalesPerson, because ambiguity.
When I filter branch using slicer, only one of Customer or Salesperson got filtered according to which relationship is active.
Is there any workaround to this situation? Thanks.
This is a good example of how the snowflake schema differs from the star schema. In a common DBMS, a snowflake schema is used. But in data analytics, a star schema is a better choice. The approach I would take is to add branchname to tables Customer and SalesPerson (and remove branchid from these two tables). You can then remove the Branch table. The tables Customer and SalesPerson have a 1:* relationship with Transaction, enabling you to filter using any of the fields in Customer and SalesPerson (including branchname).
Proud to be a Super User!
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 55 | |
| 45 | |
| 38 | |
| 16 | |
| 14 |
| User | Count |
|---|---|
| 87 | |
| 68 | |
| 38 | |
| 29 | |
| 26 |