> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v7/functions/conversion/getdatecomponents-date.md).
# GetDateComponents (Date)
| **Name** | ***GetDateComponents*** |
| ----------- | ------------------------------------------------------------------------- |
| Syntax | GetDateComponents (Date) |
| Purpose | To return a structure providing individual date components. |
| Description | Gets a structure representing individual date components. |
| Return Type | DateComponents |
| Parameters | dateTime \[System.DateTime] – Date time for which components are required |
.png)
**Example**
We have an *Orders* dataset with the *OrderDate* field.
In this example, we will pass this field to the function transformation object to get the date components.
.png)
Right-Click on the function transformation object and select *Preview Output.* In the output, you can see that each date from the *OrderDate* field has been separated in the different date components.
---
# 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://documentation.astera.com/astera-data-stack-v7/functions/conversion/getdatecomponents-date.md?ask=&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.
.png)
.png)