When doing a left join, I expect to see null results for rows that do not have a matching value on the join column.
At the analysis level, you can apply a filter to see all values, including nulls. So given the values for column TYPE. Values are A, B or NULL (for rows without matching value). I can apply a filter to see B AND NULL.
However, at the dataset level, as soon as a filter is applied. ALL NULL ROWS are immediately hidden. This is likely because there is not an explicit option to include nulls when filtering at the dataset level.
See image 1, no filter applied, null rows appear.
Image 2 has a filter for DOES NOT EQUAL type “Topic”. I would assume that all other values including nulls are expected. But I guess NOT EQUAL somehow excludes null rows?
Hi @brianpaquette ,
I’ve tried replicating you’re issue and it seems that the expected behavior if you use the Does Not Equal is that a Null will be automatically removed.
Have you tried using “Does not Contains”?
If that option is feasible to you (i.e. it will not include any other not wanted values, like “Topic Other Value 123”), that seems to work!
Andrea
Hi @brianpaquette 
any news on this one?
Is the proposed solution feasible for you?
Andrea
Hi @brianpaquette
It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.
If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.
Thank you!
Hi @brianpaquette
Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.
Thank you!
