Smart list filters on custom date fields previously fell back to raw
string comparison whenever you picked a relational operator (=, !=, >,
=, <, <=, or between). Because stored values often include a time
component, those comparisons effectively never matched and the list
came back empty. You had to combine “more than ago” / “less than ago”
filters to approximate a date range.
What’s Fixed
- Custom date filters using =, !=, >, >=, <, <=, and between now run as
real date comparisons against the stored value. - The between operator is inclusive at both ends.
- Filters tolerate legacy non-ISO values in the underlying field
instead of erroring on the query.
Migration
No action required. Existing smart lists that were returning zero
results will start returning the contacts they originally intended to
match — review them if you had built workarounds on top of the buggy
behavior.