> 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/data-table/displaying-record-name-field-as-a-link.md).

# Displaying Record Name field as a link

Turn the record name and parent records into clickable links in a screen flow Data Table with Linkify, without formula fields or URL columns.

A sales rep scanning open deals in a screen flow wants to open one in a click, or see who owns it. The Data Table does this with one toggle, **Linkify**: on the name column it links to the record itself, on a lookup column it shows the parent's name as a link to the parent.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2F5T8DNbXbfam8tOAfpTPK%2Fdata-table-tutorial-displaying-record-name-field-as-a-link-result.png?alt=media" alt="Open deals table where the deal names and the owner names are links"><figcaption><p>Deal names and owners open their records when clicked.</p></figcaption></figure>

## Before you start

* A screen with an **Avonni Data Table** fed by a Variable or Query source on Opportunity ([Learn the Basics](https://docs.avonnicomponents.com/flow/tutorials/components/data-table/learn-the-basics.md)), with Name and Owner ID among the stored fields.

## Steps

{% stepper %}
{% step %}

### Add the name column

In the Component Builder, drag **Name** (Opportunity Name) from the **Fields** tab onto the table preview. It arrives as a **Text** column.
{% endstep %}

{% step %}

### Turn on Linkify for the name

1. Click the chevron on the column header and choose **Type Attributes**.
2. Keep **Type** on **Text** and turn on **Linkify**.

Linkify links to the record only on the object's name field: Name on most objects, or the field that plays that role, such as Case Number on Case. The toggle appears on every Text column, but on any other field it changes nothing.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FOHr0ylOf3q7RqefESe8F%2Fdata-table-tutorial-displaying-record-name-field-as-a-link-linkify.png?alt=media" alt="The Type Attributes popover of the Deal column with Type set to Text and Linkify turned on" width="480"><figcaption><p>Linkify on the name column.</p></figcaption></figure>
{% endstep %}

{% step %}

### Link the parent record

1. Drag **Owner ID** onto the preview.
2. Open its **Type Attributes**, set **Type** to **Lookup**, and turn on **Linkify**.

The column now shows the owner's name instead of an Id, and the name opens the owner's user record. The **Lookup** type is offered when the table reads records, with a Variable or Query source.
{% endstep %}

{% step %}

### Save and test

Run the flow with **Debug**. Opportunity names and owner names show as links. Clicking a deal name opens the opportunity in the same browser tab.

{% hint style="warning" %}
The name link opens the record in the current tab, so the user leaves the flow screen. Put it on tables the user reads before finishing, not in the middle of a form they still have to submit.
{% endhint %}
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>Linkify is on, but the column is plain text</summary>

The column is not the object's name field. Linkify on a Text column only links the record name. For a parent record, use the **Lookup** type with Linkify on the lookup field.

</details>

<details>

<summary>I used the Url type and the link is broken</summary>

The **Url** type expects a web address, so a record name becomes a link to an address that does not exist. Use **Text** with **Linkify** for the name. Keep **Url** with **Record Link** on for a column that holds a record Id.

</details>

## Related tutorials

* [Learn the Basics](https://docs.avonnicomponents.com/flow/tutorials/components/data-table/learn-the-basics.md): build the table these links sit in.
* [Creating Row Actions](https://docs.avonnicomponents.com/flow/tutorials/components/data-table/creating-row-actions.md): open a record or a flow from a button in each row.
* [How to add images on the Data Table](https://docs.avonnicomponents.com/flow/tutorials/components/data-table/how-to-add-images-onthe-data-table.md): other column types that make a row easier to scan.


---

# 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/data-table/displaying-record-name-field-as-a-link.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.
