view_label

LookML
Version

On this Page
Docs Menu

Go to Explore Parameter List

This page refers to the view_label parameter that is part of an Explore

view_label can also be used as part of a join, described here

view_label can also be used as part of a dimension, measure, or filter field as described here

Usage

view_label is a child of
explore
explore: explore_name
...
1st
Tab
view_label: 'View Name I Want'
a string

Definition

view_label changes the way that the group of fields from an Explore’s base view will be labeled in the Field Picker:

Generally speaking, it should only be used when you need more than one view for modeling purposes, but the views represent the same entity as far as business users are concerned. For example, you might have a customer view and customer_facts view, and want them to retain those names for modeling purposes. However, it might make sense for both of them to appear as Customer to business users.

If you do not explicitly add a view_label to an Explore, the view_label defaults to the name of the Explore.

If you want to change the names of the fields themselves, you can use the label parameter.

Examples

Make the customer_facts Explore appear to be part of the customer view to business users:

- explore: customer_facts view_label: 'Customer'

Make the product_facts Explore appear to be part of the product_info view to business users:

- explore: product_facts view_label: 'Product Info'

Common Challenges

view_label Has No Effect Other Than Changing The Field Picker Appearance

When you change the view_label of an Explore, only the Field Picker is affected. The way that the Explore appears in the Explore menu, and the way that fields should be referenced in the LookML are both unchanged.

Use Proper Capitalization When Combining Multiple Views Via view_label

If you want the fields from the Explore’s base view to be merged with one of the Explore’s joined views in the Field Picker, you’ll need to make sure that the capitalization you use in view_label is correct. The capitalization you use should match how the view name appears in the Field Picker. Take this example:

- explore: product view_label: 'Product Info' joins: - join: product_info sql_on: ${product.product_id} = ${product_info.product_id}

The way that product_info will appear in the Field Picker is Product Info; each word is capitalized, and underscores and changed to spaces. For this reason, we used view_label: 'Product Info' instead of view_label: 'product_info'.

A field’s view_label takes precedence over an Explore’s view_label

If a field in an Explore has a view_label, the field will appear under its view_label, not the Explore’s view_label. Take this example below, where both an Explore and a dimension have view_label values. The dimension appears under its view_label, not the Explore’s view_label:

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