This page refers to the
fromparameter that is part of an Explore.
fromcan also be used as part of a join, described on this documentation page.
Default ValueA view whose name matches the Explore’s name
AcceptsThe name of an existing view
from determines the view that will define the fields of an Explore. If
from is omitted, Looker will assume that the underlying view name is the same as the Explore name. Typically
from is only used if you want the Explore and its fields to have a different name than the underlying view.
To make this more clear, consider an example where a dimension called
order_value has been created in a view called
- This field would typically appear as UNDERLYING VIEW Order Value in the Explore UI, and would be referenced in LookML with
- In the usage example given above, the field would appear instead as NEW ALIAS NAME Order Value and be referenced as
Add an option to the Explore menu called Customer based on the view called
label Are Often Confused but Have Different Behaviors
As seen above,
from has many effects on the way that an Explore is labeled and the way that fields are referenced. There is also a
view parameter and a
label parameter that have similar, but different, effects.
You should use this option if you want to create multiple Explores from the same view and also want to reference fields differently for each Explore:
You should use this option if you want to create multiple Explores from the same view, and you want to reference fields the same way for each Explore:
You should use this option if you don’t need to create multiple Explores from the same view, but want the Explore’s name to appear differently in the Explore menu:
Things to Know
from Is Rarely Used with
It’s not very common to use
from to re-name an Explore. Although there are legitimate use cases, if you find yourself wanting to use this parameter, consider if you can simply rename the underlying view instead. It’s much more common to rename joins using the join-level