fixed

Calendar V2 Filter Enhancement: Custom Date Range Bug Fix

Released: May 27, 2025

Overview

Issue:

We identified an issue affecting two Calendar V2 custom-date-filter options:

"is before"
"is on or after"

These filters weren't functioning correctly because our underlying LookML logic expected both a start and an end date, but these options inherently provide only one date.

Impact:

All explores utilizing Calendar V2 dimensions were affected.

Solution

We implemented a fix to update the logic so that it automatically fills in missing dates, ensuring that both filters always work correctly without manual adjustments:

"is before"
now defaults to a start date of
Jan 1, 2000
when start date is null.
"is on or after"
now defaults to an end date of
today's date
when end date is null.

Technical Details

Prior Logic:

This logic required both start and end dates, leading to errors when only one was provided.

  {% if date_filter_custom._is_filtered %}
    {% date_start date_filter_custom %}
  {% elsif date_filter_preset._is_filtered %}
    {% date_start date_filter_preset %}
  {% else %}
    ${TABLE}.current_period_start
  {% endif %}

New Updated Logic:

Start Date Adjustment:

  {% if date_filter_custom._is_filtered %}
    COALESCE({% date_start date_filter_custom %},'2000-01-01')
  {% elsif date_filter_preset._is_filtered %}
    {% date_start date_filter_preset %}
  {% else %}
    ${TABLE}.current_period_start
  {% endif %}

End Date Adjustment:

  {% if date_filter_custom._is_filtered %}
    DATEADD(day, -1, COALESCE({% date_end date_filter_custom %}, ${todays_date}))
  {% elsif date_filter_preset._is_filtered %}
    {% date_end date_filter_preset %}
  {% else %}
    ${TABLE}.current_period_end
  {% endif %}

Recommended Actions

Developers should verify custom explores that utilize these filters to ensure compatibility.
Update internal documentation as needed.

Support

For any questions or issues, please reach out via support or comment below.