User Guide Getting Started Help Center Documentation Community Training
New LookML
Old LookML
New LookML


view: view_name {
  dimension: field_name {
    suggest_dimension: dimension_name



Possible Field Types

Dimension, Dimension Group, Measure, Filter, Parameter


A fieldname in the current view or viewname.fieldname

Special Rules

To refer to a field in another view, use viewname.fieldname where viewname is a view joined in the Explore


This parameter 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.


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: }

In this example, rather than a different Explore, the suggestion uses a dimension in another view joined to the same Explore:

dimension: event_company_name { type: string sql: ${TABLE}.event_company_name ;; suggest_dimension: }