Hi,
(Sample file here: https://drive.google.com/file/d/0B9pNjpDQKy_LbUctSVJZODhaV28/view?usp=sharing)
I have encountered a possible bug when I follow these steps in Power Query:
The problem is that step 3 appears to have no effect: the row with null cannot be filtered out. Even filtering on some other specific value leaves the row with null as well as rows with that specific value.
Can anyone else replicate this? Planning to send a frown.
P.S. I know that using JoinKind.Inner in the first place would have the effect of excluding the Product=null row, but was still bothered by this apparent bug
(Sample file here: https://drive.google.com/file/d/0B9pNjpDQKy_LbUctSVJZODhaV28/view?usp=sharing)
I have encountered a possible bug when I follow these steps in Power Query:
- Merge two tables using Table.NestedJoin with JoinKind.RightOuter
(in my example I have joined Products & Sales tables, joined on Product column). - In the resulting table, as expected, there is a row with null in the Product column (corresponding to rows from Sales with Products that don't appear in the Product table).
- Then try to filter out the row with null in the Product column using Table.SelectRows.
The problem is that step 3 appears to have no effect: the row with null cannot be filtered out. Even filtering on some other specific value leaves the row with null as well as rows with that specific value.
Can anyone else replicate this? Planning to send a frown.
P.S. I know that using JoinKind.Inner in the first place would have the effect of excluding the Product=null row, but was still bothered by this apparent bug