Skip to main content
This parameter controls how child dimension labels display within a group of dimensions, such as fields created from denesting JSON.

​
Syntax

<dimension_name>:
  skip_parent_label: <always | never | explicit_child_label>

​
Properties

​
dimension_name
object
The name of the parent dimension. Dimension names must:
  • Be unique within the view
  • Start with a letter
  • Contain only alphanumeric characters and underscores

​
Examples

Consider this example of a nested JSON field: 
order_info:
  sql: "PARSE_JSON(CONCAT('{\"status\":\"', ${ecomm__order_items.status} ::
    STRING, '\", \"email\":\"', ${ecomm__users.email}, '\", \"state\":\"',
    ${ecomm__users.state}, '\"}'))"
If you were to denest the parent order_info field, it would create three child fields: status, email, and state. The following examples will use this field to demonstrate how the skip_parent_label parameter would work.

​
Always skip parent label

All child dimensions without parent label prefix
order_info:
  skip_parent_label: always
With this setting, child dimensions appear as:
  • status (not Order info Status)
  • email (not Order info Email)
  • date (not Order info State)

​
Never skip parent label

All child dimensions with parent label prefix
order_info:
  skip_parent_label: never
With this setting, all child dimensions include the parent label:
  • Order Info Status
  • Order Info Email
  • Order Info State

​
Skip parent label for explicit child labels

Selective label prepending based on explicit labels
order_info:
  skip_parent_label: explicit_child_label

order_info_custom:
  sql: ${order_info}
  label: Custom Order Info
  group_label: Order info
With this setting:
  • order_info_custom displays as Custom Order Info because it has an explicit label
  • Child dimensions have Order Info prepended as they don’t have explicit labels. For example, Order Info State
  • group_label - Nests fields in the field browser
  • label - Sets a custom display label for a field