# Creating an override style filter

**URL:** <https://community.omni.co/t/creating-an-override-style-filter/137>\
**Category:** Patterns\
**Created:** [August 9, 2024, 6:18pm UTC](https://community.omni.co/t/creating-an-override-style-filter/137 "2024-08-09T18:18:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jack](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.omni.co/jack/32/14_2.png) [@jack](https://community.omni.co/u/jack)\
**Post date:** [August 9, 2024, 6:18pm UTC](https://community.omni.co/t/creating-an-override-style-filter/137/1 "2024-08-09T18:18:40Z")

</div>

Occasionally, you may want a query view to have a default filter set from the base table, and then be able to override that filter. We can use mustache templating within the definition of the query view to achieve this. The below structure allows for a filter to be applied as a default from the base\_table, which is then overridden by any filter selection on the query\_view. In this case, the override\_field is likely a filter only field defined within the query view.

```auto
{{# query_view.override_field.filter}} field_to_filter_on {{/ query_view.override_field.filter}}
  {{^ query_view.override_field.filter}} {{# base_table.default_field.filter }} field_to_filter_on {{/ base_table.default_field.filter }}
  {{/ query_view.override_field.filter}}

```