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

# always_having_filters

> Applies a filter to aggregated results (measures) in a query using filter syntax.

This parameter is functionally identical to [`always_having_sql`](/modeling/topics/parameters/always-having-sql), but uses [filter syntax](/modeling/filters) instead of SQL.

<Note>
  This parameter must reference **measures**, not dimensions. To filter on non-aggregated fields, use [`always_where_filters`](/modeling/topics/parameters/always-where-filters) instead.
</Note>

When defined, a filter will be inserted into the `HAVING` clause of the generated SQL block of all queries in the topic. Users with the **Querier** role can't change this filter and it will be visible only in the underlying SQL of any queries. This filter is additive to any measure filters specified in the workbook.

## Syntax

```yaml theme={null}
always_having_filters:
  <field_name>:
    <filter_operator>: <value>
```

## Properties

<ParamField path="always_having_filters" type="object" required>
  A map of measure names to filter conditions that are applied to the `HAVING` clause of all queries in the topic using filter syntax.

  <Expandable title="filter structure" defaultOpen="true">
    <ParamField path="field_name" type="object" required>
      The measure to filter on, specified as `view_name.measure_name`.

      <Expandable title="filter operators" defaultOpen="true">
        <ParamField path="filter_operator" type="any" required>
          The filter operator and value to apply. Refer to the [filter syntax documentation](/modeling/filters) for available operators like `is`, `not`, `greater_than`, `less_than`, etc.
        </ParamField>
      </Expandable>
    </ParamField>
  </Expandable>
</ParamField>

## Examples

```yaml theme={null}
always_having_filters:
  users.count:
    greater_than: 5
```