> 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

## Overview

Make Record Name fields clickable and display Parent Record names as links in the [Avonni Data Table](/flow/flow-components/data-table.md) component. Using the 'Linkify' toggle, you can easily turn these fields into interactive elements, eliminating the need for extra formula fields or workarounds.

### Displaying Record Name field as a link

Specific fields (like the name field) can be displayed as a link. A toggle **`Linkify`** will appear below the Type Attributes section.

{% hint style="info" %}
**Linkify** is only displayed for the Record Name of the object.
{% endhint %}

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2Fgit-blob-4cecc6211389e55f5943a8d287147ced84155474%2F2023-03-12_21-18-23.png?alt=media" alt=""><figcaption></figcaption></figure>

### Displaying Parent Record names with a link

The Avonni Data Table component natively supports the display of parent record names, eliminating the need for additional formula fields or other workarounds.

* Drag the Parent record field in the Data Table
* Select "Lookup" as Type
* Check "Linkify" to display the parent records as a link

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2Fgit-blob-f81ca585bf4e9b43f0a11644d65baa7b3325239b%2F2023-09-19_09-23-25.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Lookup fields are not editable on the Avonni Data Table.
{% endhint %}


---

# 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.