User Guide Getting Started Help Center Documentation Community Training
New LookML
Old LookML
New LookML
  
English
日本語
suggest_explore

Usage

view: view_name {
  dimension: field_name {
    suggest_explore: explore_name
  }
}

Hierarchy

suggest_explore

Possible Field Types

Dimension, Dimension Group, Measure, Filter, Parameter

Accepts

The name of an Explore

Definition

This parameter, used with suggest_dimension, changes how Looker generates suggestions for a filter field or a dimension of type: string when someone uses that field to filter a query.

Looker typically generates these suggestions by executing the following query on the filter field:

SELECT DISTINCT <field name> FROM <table> LIMIT 1000

If the field is in a particularly large table, this query can be too slow or create too large a database load.

By using suggest_dimension you can make Looker query an alternative dimension for the suggestion values. If that dimension lives in a different Explore, suggest_explore lets you tell Looker where to find it; otherwise, suggest_explore is not required.

Examples

In this example, instead of looking through a huge list of user names from the event table, we’ve told Looker to query the names from a user table instead:

dimension: event_user_name { type: string sql: ${TABLE}.event_user_name ;; suggest_explore: user suggest_dimension: user.name }

Top