Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
I want to relate two tables 'OE' and and 'Salary' with 1:n relationship.
'OE' contains the column with unique Key OE3 and 'Salary' contains the column OE3.
If i want to activate the relationshop, there comes the meesage that the 1:n is not possible.
What´s the reason?
Solved! Go to Solution.
No, last step creating table 'OE' ist deleting duplicates.
sorry, you are right, there were duplicates. Problem was there were two values, one without last <Space> one with last <space>. I have found it. Interestingly in Excel and Power BI it is be used as identic value. Only powerquery knows, that therae ar two different values. Now I have deleted the last space, delted duplicates and now I can use 1:n relationship.
Yup, I have encountered this with SQL Server, two values 'Contoso' and 'Contoso ' are considered the same in SQL Server, but Power Query doesn't considers this so it shows both Contoso in the drop down.
DECLARE @test TABLE (Brand VARCHAR(20))
INSERT INTO @test
VALUES
('Contoso'),
('Contoso ' ),
('Contoso ')
SELECT DISTINCT *
FROM @test
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 4 | |
| 4 | |
| 4 |