> ## 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/views/parameters/fill-fields",
  "feedback": "Description of the issue"
}
```

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

</AgentInstructions>

# fill_fields

> Fills an enumerated list to ensure all values are represented in the dataset.

This parameter is useful when you want to use a [query view](/analyze-explore/saved-views) as a base table for other date objects and want to ensure all dates are represented in the data set, avoiding any ad hoc date series building.

<Note>
  To fill, Omni requires knowledge of the beginning and end of the fill set (e.g., `last 200 days`). If the date series is unbounded on either side, Omni will not fill the dimension.
</Note>

## Syntax

```yaml theme={null}
fill_fields: [ <view_name>.<field_name>, ... ]
```

## Properties

<ParamField path="fill_fields" type="array">
  A list of dimensions, specified as `view_name.field_name`.
</ParamField>

## Examples

```yaml title="Fill date dimension in query view" highlight={8} theme={null}
query:
  fields:
    [ "lead.created_date[week]", lead.count ]
  base_view: lead
  filters:
    lead.created_date:
      time_for_duration: [ 30 weeks ago, 30 weeks ]
  fill_fields: [ "lead.created_date[week]" ]
  sorts:
    - field: lead.created_date[week]
```