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!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
trying to create relationship between two tables. can anyone tell me why its giving me this error and what i need to do to connect it? i am trying to link the corp ae table to corp ae table but its not linking. i know there columns in both that match becasue i checked them but why dosnt it detect it?
i cannot have a unique value because my corp ae table has multiple values and i cannot remove it.
for example
a product 1 jan sale
a product 1 feb sale
b product 2 ...
To establish a relationship between two tables, the columns have to have a 1:1 or 1:Many relationship with the data they contain.
Based on the screen shot, the columns you would like to create a relationship between do not have a 1:1 or 1:Many relatioship. I can't tell for sure with just 3 rows of data, but it looks like you have a Many:Many (each unique response appears many times in each column) type relationship, which does not work.
If you are looking to pull Sales Office/Sales Market from 'Sheet 1' in to 'Category Report' and the list of unique names in column [Corp AE] is the same for both tables, you would need to de-duplicate 'Sheet 1' based on column [Corp AE] so that each unique name in the column only appears one time. If that is something you are able to do, you can establish a 1:Many relationship between the two tables.
- Chris
trying to create relationship between two tables. can anyone tell me why its giving me this error and what i need to do to connect it? i am trying to link the corp ae table to corp ae table but its not linking. i know there columns in both that match becasue i checked them but why dosnt it detect it?
@ankitpatira is right, it's about the keys.
What I end up doing is concatenating PK and FK as a new column and this column will be the new PK for the connected tables. But things get messy with complex data.
Allowing multiple keys relationship which is not supported is the solution, vote for it here if you find it beneficial
https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/11428449-allow-database-multiple-...
And if you find something easier, let us know.
@rjunai200 Basically you need to consider it as PK FK relations in your database tables. What error means is that in one of your tables there has to be unique values which will be your PK table and other will be FK table.
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 |
|---|---|
| 61 | |
| 59 | |
| 42 | |
| 18 | |
| 15 |
| User | Count |
|---|---|
| 105 | |
| 99 | |
| 38 | |
| 29 | |
| 29 |