> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Cognite Data Fusion (CDF) is an industrial DataOps platform. Prefer English docs unless the user asks for another locale.
> Follow /_llms/ index links recursively until you reach page URLs ending in .md. Fetch those Markdown twins instead of HTML.
> For REST APIs, default to calendar version 20230101 (stable). Use 20230101-beta or 20230101-alpha only if the user is on a preview API. Cite paths under /api-reference/concepts/<version>/ and the Cdf-Version header. Prefer the Python SDK (cognite-sdk) unless the user is in JavaScript/TypeScript.
> Start here by task: platform overview /cdf/index.md; data modeling /cdf/dm/index.md; data integration /cdf/integration/index.md; access /cdf/access/index.md; CDF Toolkit /cdf/deploy/cdf_toolkit/index.md; REST quickstart /dev/quickstart.md; Python SDK /dev/sdks/python/index.md; Atlas AI /cdf/atlas_ai/concepts/index.md; Flows apps /cdf/flows/index.md; Aura UI /cdf/aura/index.md; MCP and IDE setup /dev/guides/ide_ai_integration.md.
> For implementation work, also load /skill.md.

# Date picker

> Date picker allows the user to select a specific date either from a calendar or via the input.

<Badge color="blue">v1.0.0</Badge> | [View Date picker in Storybook](https://master--695bb4b1b8041ae09768950a.chromatic.com/?path=/docs/primitives-datepicker--docs) · [View Time picker in Storybook](https://master--695bb4b1b8041ae09768950a.chromatic.com/?path=/docs/primitives-timepicker--docs) · [View Date range picker in Storybook](https://master--695bb4b1b8041ae09768950a.chromatic.com/?path=/docs/primitives-daterangepicker--docs) · [View Date time range picker in Storybook](https://master--695bb4b1b8041ae09768950a.chromatic.com/?path=/docs/primitives-datetimerangepicker--docs)

## When to use

* **When users need precision:** If the user needs to select an exact date or time.
* **To ensure proper formatting:** Avoids input errors by enforcing a standard format.
* **When date is the primary input:** If date is the core action.

## When to use something else

* **When looking for recent or real time data:** Consider allowing the user to sort by recent activity or toggle on "live data".
* **For relative date queries:** While a Date picker may be helpful, consider adding shortcuts to the picker for a quicker selection, such as "Last week", "Last month" and "Last year".
* **When entering fixed or recurring time values:** Consider allowing for cron expressions or pre-set date and time stamps users can choose from.
* **When exact timing and format is not important:** When users leave comments or descriptions where they reference a date or time but the formatting does not matter, provide a simple [Input](/cdf/aura/primitives/input) or [Textarea](/cdf/aura/primitives/textarea).

## Dos and don'ts

* Do allow for shortcuts when it would help speed up date selection.
* Don't change the predefined date format.
* Don't truncate dates inside the Input.

## Behavior

* If the date value has constraints (e.g. only past dates), disable invalid dates rather than letting users select them and fail on submit.
* Opening the control reveals a date picker anchored to the field; choosing a value commits it in the configured locale format.
* Keyboard users must be able to type valid values and open the picker without relying on the mouse alone (implementation-specific shortcuts allowed).

## Often used with

[Label](/cdf/aura/primitives/label), [Helper text](/cdf/aura/primitives/helper-text); field shell matches [Input](/cdf/aura/primitives/input) patterns (prefix/suffix/icon) when the implementation provides slots.

## Accessibility

* Programmatically link the popover trigger button to its visual label using matching `id` and `htmlFor` attributes on the [Label](/cdf/aura/primitives/label) component.
* Pass `aria-invalid="true"` to the trigger button when form validation fails, and link error text via `aria-describedby`.
* Format the trigger text clearly (e.g., "Jan 12, 2026" instead of raw ISO strings) so screen readers announce an informative accessible name when focused.