> 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-v6/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 |

![](https://github.com/astera-software/Astera_Data_Stack_v9/blob/main/.gitbook/assets/0%20\(18\).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.

<figure><img src="https://github.com/astera-software/Astera_Data_Stack_v9/blob/main/.gitbook/assets/1%20(19).png" alt=""><figcaption></figcaption></figure>

![](https://github.com/astera-software/Astera_Data_Stack_v9/blob/main/.gitbook/assets/2%20\(19\).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.

<figure><img src="https://github.com/astera-software/Astera_Data_Stack_v9/blob/main/.gitbook/assets/3%20(13).png" alt=""><figcaption></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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.astera.com/astera-data-stack-v6/functions/conversion/getdatecomponents-date.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
