Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
I'm trying to migrate a report I made in SQL into PowerBI but as I do it I'm finding that many of the joins won't work in PowerBI. To give one example, I am not able to join two tables together where the joining columns are not unique, however this is not a problem in SQL. Is the only solution to do all my SQL coding on the back end to create a flat file that I can bring into BI to visualize, or is there something Power BI can do here?
Solved! Go to Solution.
Yes for relationship, you need unique value in master table.
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
Use the query editor steps that set up a distinct table; then join the tables to the distinct table rather than directly to each other.
yes this is different than the database approach - but you can still achieve the many:many relationship this way.
another difference is single joins only (unless my info is out of date; have been off line for a few months and the application updates frequently) - this is handled by using the query editor to create a new merged single column (from the columns that were joined in the database) in both tables - and you join these new merged columns in Power BI.
Use the query editor steps that set up a distinct table; then join the tables to the distinct table rather than directly to each other.
yes this is different than the database approach - but you can still achieve the many:many relationship this way.
another difference is single joins only (unless my info is out of date; have been off line for a few months and the application updates frequently) - this is handled by using the query editor to create a new merged single column (from the columns that were joined in the database) in both tables - and you join these new merged columns in Power BI.
Yes for relationship, you need unique value in master table.
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
94 | |
90 | |
84 | |
70 | |
49 |
User | Count |
---|---|
143 | |
121 | |
112 | |
59 | |
58 |