On this Page
Docs Menu

Go to Field Parameter List


This parameter changes the way that suggestions are generated for a dimension or filter field when someone uses that field to filter a report.

Looker typically generates these suggestions by executing a SELECT DISTINCT query on the field. For some large tables this query can be too slow or create too large of 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, you can use suggest_explore as well. Otherwise, it is not required.


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

- dimension: event_user_id sql: ${TABLE}.event_user_id suggest_explore: user suggest_dimension:

In this example, the suggestion uses a dimension in another view joined to the explore:

- dimension: event_company_id sql: ${TABLE}.event_company_id suggest_dimension:

Still have questions?
Go to Discourse - or - Email Support