> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.omni.co/feedback

```json
{
  "path": "/modeling/dimensions/parameters/skip-parent-label",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# skip_parent_label

> Controls whether child dimension labels are prepended with the parent field label in grouped dimensions.

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

## Syntax

```yaml theme={null}
<dimension_name>:
  skip_parent_label: <always | never | explicit_child_label>
```

## Properties

<ParamField path="dimension_name" type="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

  <Expandable title="dimension_name properties" defaultOpen="true">
    <ParamField path="skip_parent_label" type="string">
      Controls whether child dimensions prepend their label with the parent field label. Options:

      * `always` - Parent label is never prepended to child dimensions
      * `never` - Parent label is always prepended to child dimensions (default when unset)
      * `explicit_child_label` - Child dimensions with an explicit label set will not have the parent label prepended, but those without explicit labels will
    </ParamField>
  </Expandable>
</ParamField>

## Examples

Consider this example of a nested JSON field:

```yaml theme={null}
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

```yaml title="All child dimensions without parent label prefix" theme={null}
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

```yaml title="All child dimensions with parent label prefix" theme={null}
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

```yaml title="Selective label prepending based on explicit labels" theme={null}
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`

## Related parameters

* [`group_label`](/modeling/dimensions/parameters/group-label) - Nests fields in the field browser
* [`label`](/modeling/dimensions/parameters/label) - Sets a custom display label for a field
