bug in Power BI Desktop (Filtering not working as expected)

[XLBob]

Filteringrelationshiplookupfact

simple sample data here, 1 fact and 1 lookup. standard relationship between lookup and fact. as you can see in very top JPG, when I select 0 from lookup, only 1 row which has traffic value 0 should have been returned. However, 2 rows have been returned. Selecting any other value will give me expected result. I assume this is a bug for the March release of Power BI desktop as I don't understand at all why it's doing this. 

[RahulYadav · Accepted solution]

Hi @XLBob,

There seems to be an issue if there are nulls in Numeric field used for joining two tables. If you convert the Traffic & Gov Traffic PA fields to "Text" then the issue is not replicating.

Thanks,

Rahul

[XLBob]

@RahulYadav,Thanks for your brilliant idea. I will give this a try next Monday. I need the Traffic value to be INT type as it's used in numeric calculation. Anyway, x1 will convert any number as text back to numbers so it doesn't concern me too much. But I still hope that MS can fix this. 

[XLBob]

@MattAllington Matt, have you come accross this?

[XLBob]

Seems like it's seeing 0 the same as NULL (blanks)

[MattAllington]

You cannot have a blank as a foreign key in a data table.

edit:  well clearly you can, but you shouldn't

[XLBob]

@MattAllington Thanks for your reply. I am not convinced by the fact that having blank as a foreign key in a data table is the reason why it's doing that. When I filter blank it's only giving me the balnk row in fact table.