This page refers to the
exploreparameter that is part of a model.
explorecan also be used as part of a dashboard filter, described on this documentation page.
explorecan also be used as part of a dashboard element. A representative example of its usage is provided on the documentation page for column chart elements.
AcceptsThe name of an existing view, or a name for the
If there is a plus sign (
+) in front of the Explore name, such as
explore: +orders, that is a refinement of an Explore. See the LookML refinements documentation page for more information.
explore adds an existing view to Looker’s menu of Explores as described on the LookML terms and concepts documentation page. As a best practice, an Explore should be defined inside of a model file.
Explores are typically named after an existing view. However, if you want to have multiple Explores based on the same view, you can add a
from parameter to the Explore. In that case, the Explore can be given any valid name, which includes only lowercase letters (a-z), digits (0-9), and underscores.
explore plays an important role in the SQL that Looker generates. Suppose a user chooses Customers from the Explore menu and runs a query. This
customers Explore is based on the view called
customers, which is associated with a database table. That table is placed in the
FROM clause of the user’s SQL query.
explore can have many child parameters that affect the display and filter behavior and that specify adding joins for the Explore. If an Explore includes one or more joins, then those joins can have join parameters that specify the desired join behavior.
Add an option to the Explore menu based on the view called
Add an option to the Explore menu called Events based on the view called
explore Needs to Reference an Existing View Name
You cannot define the database table, dimensions, measures, and other fields that are part of a view via an
explore parameter. Instead, you first need to define a view using the
view parameter. Then you can reference the name of that view in
explore Needs to Reference the View Name, Not Its Filename
Typically, the name of a view is the same as the view file where the view is defined. However, this is not required — the view and view file names can be different.
For example, suppose you had a scenario where a view called
users was defined inside of a file called
company_users. Then the view file
company_users looks like this:
You would then add the
users view to the Explore menu with:
Even though the
users view is inside of a file called
company_users, the name of the file does not matter. Only the name of the view in the
view parameter matters.
When you use a measure of
type: countin an Explore, the visualization labels the resulting values with the view name rather than the word “Count.” To avoid confusion, we recommend pluralizing your view name, selecting Show Full Field Name under Series in the visualization settings, or using a
view_labelwith a pluralized version of your view name.
Things to Know
explore Is Usually Used with Additional Parameters
It’s possible to use
explore all by itself, without additional parameters. In practice, you typically will see
explore used with additional options. For example, it’s very common to
join additional views into an Explore.
All of the additional parameters that are associated with
explore are found here. The parameters that can be used for a
join within an Explore are found here.