> ## 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.

# exclude_from_level_of_detail - Filter operators

> Keeps a filter lifted from a drilled measure out of the drill's level_of_detail subqueries.

Automatically set by Omni when you drill into a measure that has both `filters` and a [`level_of_detail`](/modeling/measures/parameters/level-of-detail) calculation. Drilling pulls the measure's filters into the drill query's `WHERE` clause; this parameter keeps a pulled filter out of the drill's `level_of_detail` subqueries, ensuring drill-through rows match the tile's aggregate.

You rarely need to set this manually, but you may see it in the YAML of a saved drill tab.

<Note>
  While similar to [`cancel_query_filter`](/modeling/filters/operators/cancel-query-filter), this parameter still applies the filter to the drill's outer results and only exculdes it from `level_of_detail` subqueries, whereas `cancel_query_filter` ignores a query filter entirely.
</Note>

## Syntax

```yaml theme={null}
query:
  filters:
    <field>:
      <filter_operator>: <value>
      exclude_from_level_of_detail: true
```

## Properties

<ParamField path="field" type="string" required>
  The field to filter on, specified in the format `view_name.field_name`.
</ParamField>

<ParamField path="filter_operator" type="varies" required>
  Any standard filter operator (e.g., [`is`](/modeling/filters/operators/is), [`not`](/modeling/filters/operators/not), [`greater_than`](/modeling/filters/operators/greater-than), etc.) with its corresponding value.
</ParamField>

<ParamField path="exclude_from_level_of_detail" type="boolean">
  If `true`, the filter still applies in the query's outer `WHERE` clause, but is excluded from any `level_of_detail` subqueries that the query's fields require.
</ParamField>

## Examples

In this example, drilling into a measure with a `status` filter and a `level_of_detail` calculation produces a query like the following:

```yaml theme={null}
query:
  fields:
    orders.order_date: order_date
    orders.distinct_days_with_high_value_orders: distinct_days_with_high_value_orders
  base_view: orders
  topic: orders
  filters:
    orders.status:
      is: "unexpectedly_out_of_stock"
      exclude_from_level_of_detail: true
```

The' `orders.status` filter is marked `exclude_from_level_of_detail: true`, so it still narrows the drill's result rows, but doesn't also narrow the `level_of_detail` subquery that computes the aggregate.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.