> 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-v9/functions/conversion/parsedate-formats-str.md).
# ParseDate (Formats, Str)
| **Name** | ***ParseDate*** |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Syntax | ParseDate (Unknown formats, String str) |
| Purpose | To parse a date based on a specified format. |
| Description | Returns a date time value if the value was successfully parsed. Otherwise returns an error. This function successively applies specified formats and returns date time value if date is parsed using any of the specified formats. |
| Return Type | DateTime |
| Parameters |
formats \[Astera.Functions.DateFormats]
str \[System.String] – String to be converted
|
.png)
**Example**
We have an *Orders* dataset with a *ShippedDate* field.
In this example, we will map this field to the string input of the function transformation object. We will also pass a specific date time format, to match the date format of the *ShippedDate* field, to the *Format1* field in the function transformation object using a *Variables* object.
Where,
*Format1* = dd/MM/yyyy hh:mm:ss tt
In the output window, you can see values from the *ShippedDate* field have been successfully parsed by the function transformation object, as the provided date time format has been matched.
.png)
---
# 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-v9/functions/conversion/parsedate-formats-str.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)