Native dashboard: Target & Comparison(Two different independent time frames) cascading dropdowns with templated filters

Looker Q&A Looker
, ,
1

In a native Looker dashboard, I need two separate, cascading dropdown groups:

  • Target: Year → Quarter → Month

  • Comparison: Year → Quarter → Month
    These should drive templated filters in LookML so I can show for example:target_flights, comparison_flights, delta, and % delta.

What I built (short)

  • LookML dims for dropdowns:
    year_string (YYYY), quarter_key (YYYY-Q#), month_key (YYYY-MM Mon)

  • Templated filters defined:
    filter: target_year/quarter/month and filter: comparison_year/quarter/month

  • Row flags using templated filters:

    dimension: target_yesno { type: yesno; sql:
  ({% if target_year._is_null %}TRUE{% else %}{% condition target_year %}${year_string}{% endcondition %}{% endif %})
  AND ({% if target_quarter._is_null %}TRUE{% else %}{% condition target_quarter %}${quarter_key}{% endcondition %}{% endif %})
  AND ({% if target_month._is_null %}TRUE{% else %}{% condition target_month %}${month_key}{% endcondition %}{% endif %}) ;;
}
# same pattern for comparison_yesno

  • Measures filter on those flags (target_flights, comparison_flights).

Dashboard setup

  • Added six Field filters (Dropdown) named exactly:
    target_year/quarter/month and comparison_year/quarter/month

  • Each is bound to the real dims (year_string, quarter_key, month_key)

  • Set linked filters inside each group (Year → Quarter → Month)

  • Tried both tile setups:

    • One tile showing both (set to “Only apply filters I select”, unchecked all six time filters)

    • Two tiles (Target tile listens only to target_*; Comparison tile listens only to comparison_*)

Problem
Even after all this, results are not correct: sometimes Comparison shows 0, or both Target and Comparison look the same, although the data exists. The cascading dropdown UI works; LookML validates.

Ask
Could someone share a minimal working example (LookML + native filter bindings + tile “listen” settings) for this pattern?
Or confirm if there’s a known limitation when using templated filters ({% condition %}) together with linked/cascading field filters on native dashboards.