> For the complete documentation index, see [llms.txt](https://docs.unifize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unifize.com/user-guide/my-inbox/checklist/linked-record/linked-table.md).

# Linked table

The Linked Table is an enhancement to the Linked Field feature in Unifize, which will allow users to display multiple related records from another process within a checklist in a structured and tabular format. This enables richer data visibility and simplifies the process of reviewing multiple linked records in one place without needing to navigate away from the checklist.

Linked Tables are particularly useful in scenarios where a record must reference multiple related entries, such as listing multiple suppliers, inspection results, or related CAPAs.

***

### How to use

To use a Linked Table, an Admin must first configure the checklist field in **Process Builder** as a Linked Record field with **table view enabled**. Once set up, users can:

1. Open a record with a checklist that includes a Linked Table.
2. Click the link icon to browse and select multiple records from the linked process.
3. View the selected records displayed as rows in a table.
4. See key fields inline, and click **view all fields** to expand the full dataset for each linked record.

Unifize now supports **embedded fields** in Linked Tables, which are shown by default in a semi-expanded state. This means:

* Admins can configure which fields are visible by default when setting up the Linked Table.
* Users will see these default fields immediately in the checklist.
* Clicking **view all fields** reveals the remaining fields from the linked record.

***

### Best practices

* Select only relevant default fields to keep the table view clean and performant.
* Use field filters to narrow down which records can be selected by users.
* Combine Linked Tables with conditional checklist logic to tailor visibility based on workflow needs.
* Avoid displaying too many fields in the default view to prevent information overload.

🖋️Edit this page


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.unifize.com/user-guide/my-inbox/checklist/linked-record/linked-table.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.