> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/date-time-picker/format-dates-and-time-zones.md).

# Format dates and time zones

Show dates, weekdays and slot times the way your users read them, with a 12-hour or 24-hour clock, the right first day of the week and the time zone.

An account manager in Chicago books onboarding calls, and so does a colleague in Paris. The Chicago team reads "9:00 AM" and starts the week on Sunday; the Paris team reads "09:00" and starts on Monday. Here you set the Date Time Picker so each reader sees dates and times in a form they recognize.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2F5P9QlhUIjhjzOw71zsq5%2Fdate-time-picker-format-dates-and-time-zones-result.png?alt=media" alt="Weekly Date Time Picker for November 16 to 22, 2026 with a Time Zone dropdown set to Eastern Time, columns Monday 16 to Friday 20 and slots from 9:00:00 AM to 4:30:00 PM"><figcaption><p>Long weekday and month names, a 12-hour clock, and the time zone picker shown above the slots.</p></figcaption></figure>

## Before you start

* A Screen Flow with a Date Time Picker. The [Date Time Picker](/flow/flow-components/date-time-picker.md) page covers the basics.
* Know what the picker takes from each user's Salesforce settings, with no configuration:

| What                    | Comes from                                                                                                     |
| ----------------------- | -------------------------------------------------------------------------------------------------------------- |
| Slot times              | The user's Salesforce time zone. The same slot shows 9:00 for a user in Chicago and 16:00 for a user in Paris. |
| Month and weekday names | The user's Salesforce language.                                                                                |
| First day of the week   | The user's locale, while **Week Start Day** is **Default**.                                                    |

## Steps

{% stepper %}
{% step %}

### Choose a 12-hour or 24-hour clock

Open the Screen element, click the Date Time Picker, and on the **Properties** tab expand **Time Format**.

* Turn on **Time Format Hour 12** for a 12-hour clock with AM and PM.
* Leave it off for a 24-hour clock. Off is the default.

The same setting applies to every user of the flow. If your users are split, pick the clock most of them read.
{% endstep %}

{% step %}

### Set how hours, minutes and seconds are written

Still in **Time Format**, set **Time Format Hour**, **Time Format Minute** and **Time Format Second** to **Numeric** or **2 Digit**. **2 Digit** adds a leading zero, so the hour reads `09` instead of `9`. Slot times always include seconds (`9:00:00 AM`): no format setting hides them.

All three default to **Numeric**.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FPyTAgOCfjPuY6Ycmuj7n%2Fdate-time-picker-format-dates-and-time-zones-panel.png?alt=media" alt="Component Builder Properties tab with Date Format set to Year Numeric, Month Long, Weekday Long, Day Numeric and Time Format set to Hour, Minute and Second Numeric with Time Format Hour 12 turned on" width="320"><figcaption><p>Date Format and Time Format groups in the Component Builder Properties tab.</p></figcaption></figure>
{% endstep %}

{% step %}

### Set how dates are written

Expand **Date Format**. These settings change the dates in the picker header and day columns.

| Setting                 | Options                                                             | Example for Monday, November 16, 2026 |
| ----------------------- | ------------------------------------------------------------------- | ------------------------------------- |
| **Date Format Weekday** | **Long**, **Short** (default), **Narrow**                           | Monday, Mon, M                        |
| **Date Format Month**   | **Long**, **Short**, **Narrow**, **Numeric** (default), **2 Digit** | November, Nov, N, 11, 11              |
| **Date Format Day**     | **Numeric** (default), **2 Digit**                                  | 16, 16                                |
| **Date Format Year**    | **Numeric** (default), **2 Digit**                                  | 2026, 26                              |

Names (**Long**, **Short**, **Narrow**) are written in each user's language, so they read "Monday" for one user and "lundi" for another. **Numeric** and **2 Digit** read the same in every language.
{% endstep %}

{% step %}

### Fix the first day of the week

Click **Advanced Options** at the bottom of the first group of properties and set **Week Start Day**.

* **Default** follows each user's locale: Sunday for most US users, Monday for most European users.
* Pick a day (**Sunday** to **Saturday**) to force the same start for everyone, for example **Monday** for a business week.
  {% endstep %}

{% step %}

### Show the time zone

In the same **Advanced Options**, turn on **Show Time Zone**. The picker adds a **Time Zone** list showing the zone its slots are displayed in, for example `-05:00 Eastern Time - New York City`. The person running the flow can pick another zone from it.

Turn it on whenever people in several time zones use the same flow. A customer on the phone with the account manager can then check that "10:00" means the same thing to both of them.
{% endstep %}

{% step %}

### Save and test

Save the flow and click **Debug**. With **Time Format Hour 12** on, **Date Format Weekday** on **Long**, **Week Start Day** on **Monday** and **Show Time Zone** on:

* the week starts on Monday,
* weekdays are spelled in full,
* slots read on a 12-hour clock with AM and PM,
* the time zone shows on the picker.
  {% endstep %}
  {% endstepper %}

## Troubleshooting

<details>

<summary>Two users see different times for the same slot</summary>

That is expected. Each user sees the slot in their own Salesforce time zone (set in their personal settings under **Language & Time Zone**). The selected value the flow receives is the same moment for both. Turn on **Show Time Zone** so each user knows which zone they are reading.

</details>

<details>

<summary>The week starts on Sunday for some users and Monday for others</summary>

**Week Start Day** is on **Default**, which follows each user's locale. Pick a day to make it the same for everyone.

</details>

## Related tutorials

* [Offer only working hours](/flow/tutorials/components/date-time-picker/offer-only-working-hours.md): limit the slots to 9:00 to 17:00, Monday to Friday.
* [Build an appointment booking flow](/flow/tutorials/components/date-time-picker/build-an-appointment-booking-flow.md): create an Event from the picked slot.


---

# 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.avonnicomponents.com/flow/tutorials/components/date-time-picker/format-dates-and-time-zones.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.
