> 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/functions/conversion/todate-string-datestr.md).
# ToDate (String dateStr)
| **Name** | ***ToDate*** |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Syntax | ToDate (String dateStr) |
| Purpose | To return a date converted from a string. |
| Description | Converts string into a date using the current culture. Either returns the converted date or returns null if the conversion fails. |
| Return Type | DateTime |
| Parameters | dateStr \[System.String] – A string containing date in the local culture format |
**Example**
In this example, we are passing a date time value in a format NOT present in the acceptable date time formats list in Astera Data Stack, to the function transformation object using a *Variables* object.
Where,
*dateStr* = MAR.8.22
{% hint style="info" %}
**Note:** The following screenshot shows the acceptable date formats in Astera Data Stack.
{% endhint %}
In the output window, you can see that the provided string has been converted into an acceptable DateTime value.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.astera.com/functions/conversion/todate-string-datestr.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 `build a script that syncs our docs to a CMS` 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.
