Dashboard cross-filtering & filter_mapping mismatch when dashboard filters come from a different explore

Looker Q&A Looker
,
1

I’m working with a Looker dashboard that includes tiles built from multiple explores, while all dashboard-level filters are defined from a single explore.

Most tiles respond correctly to dashboard filters and cross-filtering, but tiles based on other explores show inconsistent behavior (filters not applying, partial filtering, or being ignored). These tiles rely on listen: to receive dashboard filters.

Additionally, some filter mappings / linking logic are defined using fields from a different view than the one used by the dashboard filters, which may be contributing to the inconsistency.

:red_question_mark: Question

What are the recommended best practices in Looker for handling cross-filtering and dashboard filters when:

  • A dashboard uses multiple explores

  • Dashboard filters are defined from one primary explore

  • Other tiles rely on listen: to map those filters

  • Filter mappings or linking logic may reference fields from different views

Specifically:

  • Should all filter mappings always align with the same explore/view used by the dashboard filters?

  • Is it better to standardize dashboards around a single explore, or is mixing explores considered safe if listen: is configured correctly?

  • Are there known limitations or design patterns to ensure reliable cross-filtering in multi-explore dashboards?

Any guidance or recommended patterns would be very helpful.

2

At the end of the day, cross-filtering only works on tiles created from the same Explore. So your options will be pretty limited here.

Specifically:

  1. Should all filter mappings always align with the same explore/view used by the dashboard filters?

    That would be cleanest, yes!

  2. Is it better to standardize dashboards around a single explore, or is mixing explores considered safe?

    Mixing is “safe”, sure, but it won’t let you cross filter the way that you want.

  3. Are there known limitations or design patterns to ensure reliable cross-filtering in multi-explore dashboards?

    Cross-filtering in multi-explore dashboards is just not supported.

    The best I can think of for a workaround is to try to combine all of the explores into a single explore. But of course, that won’t be possible for every situation.