Field is Unknown is different to field does not equal false?
SOLVE
I'm not sure if this is specifc to the target account property, or if it happens for all checkbox type fields, but there seems to be something wrong with the not equal to filter logic:
See examples: if target account is not set, it should also show under not equal to true, should it not? At least, that's how I'd expect a true/false operator to act...
Using not equal to true, in this instance gives me no results, but using unknown gives 468 results. Surely in the case of a boolean value, not true should also include unset?? It just seems annoying because with this logic, to cater for anyone that may in future be moved from being a target account to not being a target account, I'd have to include both conditions of equals false or is unkown, and given how clumsy lists still are when it comes to handling multiple and or conditions, that becomes a real pain.
The internal team has been working to find a better solution to approach to this matter. Now we can choose to exclude objects with "no data" or include them. Please see this image-
So if you'd want to create a list of companies with "the target account is not equal to true" and the ones without having target account, you'd want to choose "include objects with no data" option.
Field is Unknown is different to field does not equal false?
SOLVE
Also, I'm somewhat confused as to what "include objects with no data" does in the two scenarios:
If the filter is set to True and "include objects with no data" is ticked, does that mean objects with no data will be regarded as true, and if the filter is set to False and "include objects with no data" is ticked, that would regard objects with no data as false?
Or does it mean regardless of whether the filter is set to true or false, objects with no data would be evaluated under a normal boolean definition (ie no data = 0 = false)?
The internal team acknowledges this behavior, however, I haven't heard any updates yet. I will @mention you when I can share more information about this!
The internal team has been working to find a better solution to approach to this matter. Now we can choose to exclude objects with "no data" or include them. Please see this image-
So if you'd want to create a list of companies with "the target account is not equal to true" and the ones without having target account, you'd want to choose "include objects with no data" option.
I tested and I was able to replicate this behavior in my account too. Let me check this with the product team and I will get back to you in this thread!
Field is Unknown is different to field does not equal false?
SOLVE
Ok, there's definitely something up with true/false fields in general: I've just tried creating a list to identify anyone not in a sequence, by any reasonable assumption, the way to do that would be to use the filter is currently in sequence = false
However, that's not what happens - see the difference between in sequence = false and in sequence = unknown. Either this has to be unexpected behaviour for a boolean field, or someone must be on some good drugs??