Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Filtering
relationship
lookup
fact
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.
Solved! Go to 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
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
@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.
Seems like it's seeing 0 the same as NULL (blanks)
You cannot have a blank as a foreign key in a data table.
edit: well clearly you can, but you shouldn't
@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.