Empty Value on a Date Field Qualifies for the Filter Condition Even Though the Filter Condition Is Looking for a Value “Before” or “On or Before”

A document by KCS Integration on behalf of bac89b007c194479a7573c01f235e47b3ecc2bbb on Nov 26, 2018Last modified by Roxann McGlumphy on Nov 26, 2018
Version 2Show Document
  • View in full screen mode

Issue Description
You have created a Smart List with a filter for a date type field and you are using the constraints either “before” or “on or before” a particular date. However, records with empty value on those field get qualified.


Issue Resolution
When you create a Smart List using a date field filter (e.g., Date of Birth, SFDC Created Date) and use the “before” or “on or before” constraints, the Smart List will also include people who have no value in said date field. This is an expected behavior as  by default Null value is treated as a timestamp with a default value (e.g Jan 1 1900). This is similar to a token having default value and this is also mentioned as a caution within our knowledge base document over here.


The work around is to use an addition filter or to make sure that the date value is populated for all the records. You can learn the importance of date stamping in this Champion blog post.