Forum Discussion
2 data sources joined with a Key whose value may be different at some instances
I personally would not use the text "NULL" in the fields and that can be confusing vs a legitimate NULL, which is really a BLANK() in DAX. Use something else, like "None." If you are using a real null (blank()) then you can still create the relationship but you'll have values show up on one side and not the other, and can make some of the visuals have blanks where you have things like item numbers or whatever.
As to case sensitivity, it depends. DAX is not case sensitive. "None" = "NONE" = "noNE"
Power Query though is case sensitive. You would want to wrap such columns with Text.Lower(), Text.Upper, or Text.Proper() to have the same case on each side of a merge.
If that is what you see in DAX, that is the text Null and null, not a real null. A real null is blank.
If you type that in Power Query, it shows up green, showing it is a keyword:
Then shows up in italics in the Power Query window
Then shows up blank in the DAX model, and would equate to the BLANK() function, and can be trapped with IsBlank(Table[Field]), or Table[Field] = BLANK() would evaluate to TRUE().
So that Null and null are text if that is DAX. If it is Power Query it is also text, as a legit null shows up as null there.
All null values will join a the same thing in Power Query, and all BLANK() in DAX will form a filter relationship with other BLANK() values.
Community SupportHi Anonymous ,
For the relationship, recommend you create the star schema instead of circle schema, so you may delete the secondary relationships among the left table 'natgas ...' and right table 'user …' .
Then create active relationship between the middle table and the right table 'user …', and change the Cross filter direction of relationships among the three tables above from Single to Both , which will take these tables treated as a single table.
In this way, when you make some changes or interact in someone table, the other table objects will return corresponding matched result. See more:Create and manage relationships in Power BI Desktop .
Best Regards,
Amy
Community Support Team _ Amy
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi v-xicaiThanks for the response! I followed the star schema instructions, but still having the issue that I mentioned with error showing up the visual with data from table2 ['Scheduler']. It's happening as edhans just confirmed that my middle "bridging" table has to have ALL the data for the "Pipeline" names- those that match perfectly besides those don't!
Best, ~Sohana