> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/pentaho-interactive-reports-cp/advanced-topics/group-and-filter-data-in-interactive-reports/add-filters/filter-on-date-fields.md).

# Filter on date fields

Use the following steps to add a filter that matches a specific value:

1. In the toolbar, click **Filters**.

   The **Filters Panel** appears above the report.
2. Click and drag a **date field** from the right pane into the **Filters** area.

   The Filters dialog box opens.
3. Next to the field name, choose a date constraint from the list, then click the small arrow on the right to display the date picker.

   To create a "date range" you must add two filters: one for the start date, and one for the end date.
4. In the date picker, choose your date.
5. Click **OK** to save your filter.

The report display updates as soon as the filter is added. The filter appears in the **Filter** box and an icon displays next to the field name in the **Data** tab. Also, the number of filters added to the report appears next to the filter icon in the toolbar.

You can edit the filter by clicking **Edit**. You can delete the filter by clicking the **Delete** button.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pba/pentaho-interactive-reports-cp/advanced-topics/group-and-filter-data-in-interactive-reports/add-filters/filter-on-date-fields.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.