# skip_drill_filter

<br />

## Usage

```
view: view_name {
  dimension: field_name {
    skip_drill_filter: yes 
  }
}
```

|---|---|
| Hierarchy [View File](https://docs.cloud.google.com/looker/docs/reference/param-view) [`view`](https://docs.cloud.google.com/looker/docs/reference/param-view-view) [Field Type](https://docs.cloud.google.com/looker/docs/reference/param-field) `skip_drill_filter` | Possible Field Types Dimension <br /> Accepts A Boolean (yes or no) <br /> |

## Definition

When users drill into a measure, the resulting dataset is filtered so that users arrive at the specific records that made up that measure. Looker achieves this by adding filters that match the dimension values in the same row as the measure. For most types of dimensions, this works well.

However, if the value of one of those dimensions changed *during* the process of drilling, this might cause the dataset to be different than the user was expecting. If a dimension may change often (likely a pre-aggregation that occurs in a frequent ETL process), you can stop it from being included in drill filters by using `skip_drill_filter`. `skip_drill_filter` accepts `true` or `false`.

## Examples

Prevent the `transactions` dimension from being included in drill filters:

    dimension: transactions {
      sql: ${TABLE}.transactions ;;
      type: number
      skip_drill_filter: yes
    }