Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
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
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 9 | |
| 8 | |
| 7 | |
| 6 | |
| 5 |