View the original community article here
Last tested: Oct 16, 2020
The following needs to be true in order for Looker to use the aggregate table on an explore query:
- The Explore query’s fields are a subset of the aggregate table’s fields (see: Field Factors). Or, for timeframes, the Explore query’s timeframes can be derived from the timeframes in the aggregate table (see: Timeframe Factors).
- The Explore query contains measure types supported by aggregate awareness (see: Measure Type Factors), *or* the Explore query has an aggregate table that is an exact match (see: Creating Aggregate Tables That Exactly Match Explore Queries).
- The Explore query’s time zone matches the time zone used by the aggregate table (see: Time Zone Factors).
- The Explore query’s filters reference fields that are available as dimensions in the aggregate table, *or* each of the Explore query’s filters matches a filter in the aggregate table (see: Filter Factors).
The SQL tab should include a comment explaining why an aggregate table wasn't used. Use the troubleshooting section of our docs to narrow it down.
One way to ensure that an aggregate table can provide accurate data for an Explore query is to simply create an aggregate table that exactly matches an Explore query. See Creating Aggregate Tables That Exactly Match Explore Queries for details.