Forum Discussion
Merging tables with Left Join returns rows with no match
Hi Anonymous
My understanding is that Null is considered as value and it matches with Null value from another table where you have two Null, therefore you get two matching values per every Null row from the first table.
To get the desired result you can replace null values with "*" or something else in the first or second table, this will be read as mismatched records by the engine.
Please see the attached for referenceBest Regards,
Mariusz
If this post helps, then please consider Accepting it as the solution.
Hi Anonymous
My understanding is that Null is considered as value and it matches with Null value from another table where you have two Null, therefore you get two matching values per every Null row from the first table.
To get the desired result you can replace null values with "*" or something else in the first or second table, this will be read as mismatched records by the engine.
Please see the attached for reference
Mariusz
If this post helps, then please consider Accepting it as the solution.
Thank you! If I replace the nulls in the left-joined table it does prevent the null fields from being in the joined set.
This is unfortunate that PBI treats nulls this way - null should be, well null. I can't see a benefit having nulls treated as values.
Hello Anonymous ,
null is a value as any other. And if in some column that is joined is present a null and on the other side as well, why shouldn't these be treated? Simple do a filter of tables before you join them and you are alright. Or do you see any problems in doing so?
If this post helps or solves your problem, please mark it as solution.
Kudos are nice to - thanks
Have fun
Jimmy
