> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/other-help-articles/formatting-dates-additional-information.md).

# Formatting Dates - Additional Information

LogicNets parts include editors that allow you to format dates, for example:

* report-item (in Assessment Framework applications)
* format data object (process part under Data Objects menu)
* dbgrid (form part node in Starter App Framework and No Framework applications)

Date formats can be specified using any of the following codes for each part of the date and/or time.

| Specifier | Replaced by                                                  | Example                  |
| --------- | ------------------------------------------------------------ | ------------------------ |
| %%        | A % sign                                                     | %                        |
| %a        | Abbreviated weekday name                                     | Thu                      |
| %A        | Full weekday name                                            | Thursday                 |
| %b        | Abbreviated month name                                       | Aug                      |
| %B        | Full month name                                              | August                   |
| %c        | Date and time representation                                 | Thu Aug 23 14:55:02 2001 |
| %d        | Day of the month, zero-padded (01-31)                        | 23                       |
| %e        | Day of the month, space-padded ( 1-31) version 7.3 on        | 23                       |
| %H        | Hour in 24h format (00-23)                                   | 14                       |
| %I        | Hour in 12h format (01-12)                                   | 2                        |
| %j        | Day of the year (001-366) version 7.3 on                     | 235                      |
| %m        | Month as a decimal number (01-12)                            | 8                        |
| %M        | Minute (00-59)                                               | 55                       |
| %p        | am or pm designation                                         | pm                       |
| %S        | Second (00-61)                                               | 2                        |
| %U        | Week number (Sunday first day of week (00-53) version 7.3 on | 33                       |
| %w        | Weekday as a decimal number with Sunday as 0 (0-6)           | 4                        |
| %W        | Week number (Monday first day of week (00-53) version 7.3 on | 34                       |
| %x        | Date representation                                          | 8/23/2001                |
| %X        | Time representation                                          | 14:55:02                 |
| %y        | Year, last two digits (00-99)                                | 1                        |
| %Y        | Year                                                         | 2001                     |


---

# 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://community-test.logicnets.com/release-9/platform-documentation/other-help-articles/formatting-dates-additional-information.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.