cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
XLBob Regular Visitor
Regular Visitor

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

filtering.JPGFilteringrelationship.JPGrelationshipLookup.JPGlookupFact.JPGfact

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. 

1 ACCEPTED SOLUTION

Accepted Solutions
RahulYadav Regular Visitor
Regular Visitor

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

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.2018-03-16_12-17-28.jpg

 

Thanks,

Rahul

 

 

 

 

6 REPLIES 6
XLBob Regular Visitor
Regular Visitor

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

@MattAllington Matt, have you come accross this?

XLBob Regular Visitor
Regular Visitor

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

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

Highlighted
Super User
Super User

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

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

 

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



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

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

@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.

RahulYadav Regular Visitor
Regular Visitor

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

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.2018-03-16_12-17-28.jpg

 

Thanks,

Rahul

 

 

 

 

XLBob Regular Visitor
Regular Visitor

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

@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.