> 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/list/show-dates-times-and-links.md).

# Show Dates, Times and Links

Show close dates, amounts and last update times in each user's own format, and turn every deal name into a link that opens the Opportunity.

Before the forecast call, a sales manager scans the open deals on a flow screen: when each one should close, how much it is worth, when someone last touched it. Typed into the item's Description, those values print the way the database stores them, such as `2026-08-28`. Placed in **Fields**, the List formats each one by type, and a **URL** mapping turns the deal name into a link to the record.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FHhPgzzOMAXWIlZMgtKz0%2Flist-show-dates-times-and-links-result.png?alt=media" alt="A list of open deals where each deal name is a link and shows its close date, amount and last modified date and time" width="480"><figcaption><p>Dates, amounts and times come from Fields, formatted for the user</p></figcaption></figure>

## Before you start

* A Screen Flow with the Avonni Flow Components package installed.
* The [List](https://docs.avonnicomponents.com/flow/flow-components/list.md) reference page, if you have not set up a List before.

## Steps

{% stepper %}
{% step %}

### Get the open deals

1. Add a **Get Records** element. **API Name**: `Get_Open_Deals`.
2. **Object**: Opportunity. Add the condition `IsClosed` **Equals** `False`.
3. **Sort Order**: Ascending, **Sort By**: `CloseDate`.
4. **How Many Records to Store**: All records. **How to Store Record Data**: Automatically store all fields.
   {% endstep %}

{% step %}

### Add the List

1. Add a **Screen** element `Pipeline_Review` and drag the Avonni **List** onto it. Give the component the API name `PipelineList`.
2. Click **Open Component Builder**.
3. In the **Properties** tab, set the **Data Source** to **Variable** and pick `{!Get_Open_Deals}`.
4. **Label** is already filled with `{{Record.Name}}` for an Opportunity. Keep it.
   {% endstep %}

{% step %}

### Put dates, amounts and times in Fields

1. In **Data Mappings**, open **Fields** and add **Close Date**, **Amount** and **Last Modified Date**. Drag them in the picker to set their order.

Each field is formatted by its type:

| Field type                | What the user sees                               |
| ------------------------- | ------------------------------------------------ |
| Date                      | The date in the user's own format                |
| Date/Time                 | Date, hours and minutes, in the user's time zone |
| Currency, Number, Percent | The number with the field's decimal places       |
| URL                       | A link the user can click                        |

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2F3E92RfrbscLFqMHCjBRm%2Flist-show-dates-times-and-links-fields.png?alt=media" alt="The Data Mappings section with the URL template, Target set to Blank, and three fields selected under Fields" width="480"><figcaption><p>The URL mapping links each deal name and Fields holds the formatted values</p></figcaption></figure>
{% endstep %}

{% step %}

### Keep the Description for text

**Description** prints exactly what the record stores, with no formatting. `{{Record.CloseDate}}` there shows `2026-08-28`, and a Date/Time field shows a long value such as `2026-08-28T14:05:00.000Z`.

Use the Description for words, such as a short sentence built from text fields, and keep every date, time, amount and link in **Fields**.
{% endstep %}

{% step %}

### Link the deal name to its record

1. In **Data Mappings**, set **URL** to `/lightning/r/Opportunity/{{Record.Id}}/view`. The item label becomes a link.
2. Set **Target** to **Blank**, so the record opens in a new tab and the flow stays where it is. The default, **Self**, replaces the page the flow runs on.
3. For more links on the same item, add entries under **Infos**. Each one has its own **Label**, **URL** and **Target**.
   {% endstep %}

{% step %}

### Flag deals with an icon (optional)

**Annotation Icons** puts small icons on each item. Add one and either pick a single icon for every item, or map it to a text field that holds an icon name.

> **Example:** a text formula field on Opportunity, `IF(CloseDate < TODAY(), "utility:warning", "utility:clock")`, shows a warning on every deal whose close date has passed.
> {% endstep %}

{% step %}

### Save and test

1. Save the flow and click **Debug**.
2. Each deal shows its close date and amount, and its last update with the time. A user with another locale sees the dates in their own format.
3. Click a deal name: the Opportunity opens in a new tab.
   {% endstep %}
   {% endstepper %}

## Troubleshooting

<details>

<summary>A date shows as 2026-08-28, or as a long value with a T and a Z</summary>

The field sits in the **Description** or the **Label**, which print the stored value. Move it to **Fields**.

</details>

<details>

<summary>The time is a few hours off</summary>

**Fields** shows times in the time zone set in the running user's personal settings, which is the expected reading for that user. Check the time zone of the user you test with.

</details>

<details>

<summary>Clicking the item does nothing when the flow runs in an Open Flow Dialog</summary>

A **Navigate** interaction on **Item Click** does not open the record when the flow runs inside an **Open Flow Dialog**. Use the **URL** mapping from the steps above instead: the link works in the dialog too.

</details>

<details>

<summary>The record opens and the flow disappears</summary>

**Target** is on **Self**, the default, so the record replaces the page the flow runs on. Set it to **Blank**.

</details>

## Related tutorials

* [Search, Filter and Paginate a List](https://docs.avonnicomponents.com/flow/tutorials/components/list/search-filter-and-paginate.md): the same pipeline list, made easy to search once it grows.
* [Act on a Row](https://docs.avonnicomponents.com/flow/tutorials/components/list/act-on-a-row.md): add buttons to each deal and route the flow on the one clicked.
* [Build a Checklist That Saves](https://docs.avonnicomponents.com/flow/tutorials/components/list/build-a-checklist-that-saves.md): a List whose ticks are written back to Salesforce.


---

# 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/list/show-dates-times-and-links.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.
