> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/formula-syntax/identifiers/column.date.md).

# COLUMN.DATE

Extracts the date associated with a measure or column header for use in calculations.

The **COLUMN.DATE()** function returns the date derived from the date dimensions in a measure or column header. It retrieves the date based on the column’s date hierarchy, such as year, quarter or month.

### Example <a href="#example" id="example"></a>

#### 1. Extract date from column hierarchy

We want to create a new measure that displays the date derived from the column header's date hierarchy.

<figure><img src="https://3062809325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEbkCXCUXmtUq5tcnUtZE%2Fuploads%2Fw8ryuqhOThv8Yfa1fVop%2Fimage.png?alt=media&amp;token=e99edfc3-454c-4cc0-9424-e278e6056e89" alt=""><figcaption><p>Applying COLUMN.DATE()</p></figcaption></figure>

#### 2. Extract date from custom title

If user enters a date in the measure/column header's **Title,** COLUMN.DATE() returns that date from the title overriding the date derived from the column’s date dimensions.

<figure><img src="https://3062809325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEbkCXCUXmtUq5tcnUtZE%2Fuploads%2FJ3Jmiwp3rz2gJk7J5bvd%2Fimage.png?alt=media&amp;token=7a657a07-521c-442d-8576-5cd03f026aca" alt=""><figcaption><p>Applying COLUMN.DATE()</p></figcaption></figure>


---

# 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.inforiver.com/formula-syntax/identifiers/column.date.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.
