Content Component 26.1
Content Component Help

# DateFormat

The date format of the specified Date. You can use one of the following options:

- `AUTNDATE`

- `#ISODATETIME` (for details, see DateFormatCSVs)

- a string that contains one or more of the date formats in the following table.

`YY` | Year (two digits). For example, 99, 00, 01, and so on.
`YYYY` | Year (four digits). For example, 1999, 2000, 2001, and so on.
`#YY+` | Year (two or four digits). If you provide two digits, it uses the `YY` format. If you provide four digits, it uses the `YYYY` format. For example, it interprets `07` as `2007 AD` and `1007` as `1007 AD`.
`#Y` | Year (one to a maximum of 16 digits), optionally followed by `AD` or `BC`. An apostrophe (`'`) immediately before the year denotes a truncated year. For example, `2008`, `'97` (interpreted as `1997`), `97` (interpreted as `97 AD`), `'08` (interpreted as `2008`), `2008 AD`, and `200 BC`. A truncated year with a BC identifier is not valid (`'08 BC`).
`#FULLYEAR` | Year (one to a maximum of 16 digits). For example, `8`, `98`, `108`, `2008`, each of which is taken literally. The year is taken relative to the common EPOCH (0 AD).
`#ADBC` | Time period. For example, `AD`, `CE`, `BC`, `BCE`, or any predefined list of EPOCH indicators. Typically, the year specified in the above formats is interpreted as untruncated and relative to the EPOCH. For example, 84 AD is interpreted as 1984 AD, and 84 BC is interpreted as 84 BC. The only exception to this is when you use both `#YY+` and `#ADBC`. In this case, the format is interpreted as untruncated, even if the year was set to truncated by `#YY+`. For example, 99 AD is interpreted as the year 99 AD. OpenText recommends that you use only `YY`, `YYYY`, or `#FULLYEAR` with `#ADBC`.
`LONGMONTH` | A long month, for example, `January`, `February`, and so on.
`SHORTMONTH` | A short month, for example, `Jan`, `Feb`, and so on.
`MM` | Month (two digits). For example,`01`, `10`, `12`, and so on.
`M+` | Month (one or two digits). For example, `1`,`2`,`3`,`10`, and so on.
`DD` | Day (two digits). For example, `01`, `02`, `03`, `12`, `23`, and so on.
`D+` | Day (one or two digits). For example, `1`, `2`, `12`, `13`, `31`, and so on.
`LONGDAY` | Two digits with a postfix. For example, `1st`, `2nd`, and so on.
`HH` | Hour (two digits). For example, `01`, `12`, `13`, and so on.
`H+` | Hour (one or two digits).
`NN` | Minute (two digits).
`N+` | Minute (one or two digits).
`SS` | Second (two digits).
`S+` | Second (one or two digits).
`ZZZ` | Time zone, for example, `GMT`, `EST`, `PST`, and so on.
`ZZZZZ` | Time difference (one to nine digits). For example, `+04` denotes four hours ahead of UTC. Other examples include `+4`, `+04`, `+0400`, `+0400 MSD` (the string `MSD` is ignored). A further example is `+030`. In this case the time difference is interpreted as 30 minutes. This option accepts a single `Z` character in a date string as UTC. It accepts time zones between `-1300` and `+1500`.
`#PM` | An `AM` or `PM` indicator (two characters). For example, `2001/09/09 02:46:40 PM`.
`#S` | A space.

Actions: | DateConvert
Type: | String
Default: |
Example: | `action=DateConvert&Date=10/05/1234&DateFormat=DD/MM/YYYY`
See Also: | Date DateFormatCSVs

Copyright 2025 Open Text
Version 26.1 | Last updated January 2026

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery Content Component 26.1

Topic Title: DateFormat