cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
KishNSI
Frequent Visitor

Joins on same primary key field are returning no matches, all null columns

You can see from the screenshot below that it is stating there are no matches even before the merge. After it merges, the columns from the second table are filled with nulls. It is an integer primary key field shared in both tables; I have no clue what the problem could be.

 

image.png

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Joins on same primary key field are returning no matches, all null columns

How do you know there are matches?  I don't see any in the image. 



* Matt is a Microsoft MVP (Power BI) and author of the Power BI Book Supercharge Power BI.

View solution in original post

2 REPLIES 2

Re: Joins on same primary key field are returning no matches, all null columns

How do you know there are matches?  I don't see any in the image. 



* Matt is a Microsoft MVP (Power BI) and author of the Power BI Book Supercharge Power BI.

View solution in original post

KishNSI
Frequent Visitor

Re: Joins on same primary key field are returning no matches, all null columns

It turns out that I was grossly misinformed as to the nature of these two views. I appreciate your question, and will go flip a table now.

Helpful resources

Announcements
Announcing the New Spanish Forum

Announcing the New Spanish Forum

Do you need help in Spanish? Check out our new Spanish community section.

April 2020 Community Highlights

April 2020 Community Highlights

Info on our Super Users, MBAS content and badges, and updates to our support articles. - Read the full Community Highlights.

MBAS Gallery 2020

MBAS Gallery 2020

Watch Microsoft Business Applications Summit sessions on-demand.

Top Solution Authors
Top Kudoed Authors