> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/generic/date-operations/change-date-format.md).

# Change Date Format

This is a pre-built Action located under the **@Generic Element**. The functionality of this Action in Avo Assure is to change the format of the given date based on the format specified in the input value column. The execution status is then stored in a dynamic variable.

## Syntax

**Input Value**: `<date>;<current format>;<required format>`

| Argument                                | Description                                                                                                                                                                                   |
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<date><br>(Required)</p>            | Provide the date that needs to be converted.                                                                                                                                                  |
| <p>\<current format><br>(Required)</p>  | Provide the current format of the given date.                                                                                                                                                 |
| <p>\<required format><br>(Required)</p> | <p>Provide the format in which you want the date to be converted.<br>Supported date formats are:</p><ul><li>dd/MMM/yyyy</li><li>MMM/dd/yyyy </li><li>dd/MM/yyyy </li><li>MM/dd/yyyy</li></ul> |

**Output Value**: `<Dynamic Variable>;<Dynamic Variable>(Optional)`

| Argument                                 | Description                                                       |
| ---------------------------------------- | ----------------------------------------------------------------- |
| <p>\<Dynamic Variable><br>(Required)</p> | This dynamic variable stores the converted date format.           |
| <p>\<Dynamic Variable><br>(Optional)</p> | This dynamic variable stores the status as **True** or **False**. |

### **Example: Converting a Date into a Different Format**

In this example, we explain how to convert a date from one format to another.

* **Action**: Change Date Format
* **Input Value**: 12/11/2025;dd/MM/yyyy;MM/dd/yyyy
  * The first argument (**12/11/2025**) specifies the original date.
  * The second argument (**dd/MM/yyyy**) specifies the current format of the input date.
  * The third argument (**MM/dd/yyyy**) specifies the required output format.
* **Output Value**: {Formatted Date}
  * The converted date (11/12/2025) is stored in this **{Formatted Date}** dynamic variable.
  * If a second output variable is provided, then action returns the status as **True** or **False**:
    * **True**: If the date format is converted successfully.
    * **False**: If the conversion fails due to an invalid date or incorrect format.
* **Logical Explanation**: The **Change Date Format** action fetches the value from the **Input Value** column (**12/11/2025;dd/MM/yyyy;MM/dd/yyyy**), converts the date from the current format (dd/MM/yyyy) to the required format (MM/dd/yyyy), and stores the resulting date (11/12/2025) in the **{Formatted Date}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FCwFne7Ce3wTv94lMfQ2y%2Fimage.png?alt=media&amp;token=7a9fad36-5d24-452c-a47c-5726b373e19a" alt=""><figcaption></figcaption></figure>

#### Knowledge Bites:

Here are some examples of different date formats:

<table><thead><tr><th width="168.20001220703125">Date formats</th><th width="347.1331787109375">Input Value</th><th>Result</th></tr></thead><tbody><tr><td>dd/MM/yyyy</td><td>08/11/2025;dd/MM/yyyy;dd/MMM/yyyy</td><td>08/Nov/2025</td></tr><tr><td>MM/dd/yyyy</td><td>11/08/2025;MM/dd/yyyy;MMM/dd/yyyy</td><td>Nov/08/2025</td></tr><tr><td>dd/MMM/yyyy</td><td>11/Nov/2025;dd/MMM/yyyy;dd/MM/yyyy</td><td>11/11/2025</td></tr><tr><td>MMM/dd/yyyy</td><td>Nov/11/2025;MMM/dd/yyyy;MM/dd/yyyy</td><td>11/11/2025</td></tr></tbody></table>


---

# 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://docs.avoautomation.com/avo-assure/actions/generic/date-operations/change-date-format.md?ask=<question>&goal=<user_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.