> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/review-workflow/exports/custom-tables.md).

# Custom Tables

Learn how to build a custom table to export.

Use Custom Table Export to build custom tables of included studies, ready for export. Use to reproduce a spreadsheet structure of your own design, restrict output to a specific subset of studies, or control the level of detail (study, study arm, or intervention) each row represents.

For bulk exports covering every study in the nest regardless of shape — metadata, screening decisions, tags, extracted data, critical appraisal, or full-text PDFs — use [Download from Inspector](/review-workflow/study-inspector/download-from-inspector.md) instead.

### Where To Build It

The Table Builder is available in two places, and the build process is identical in both. What differs is what happens to the table once it's built:

* **On the Export page:** build for immediate download, or save the configuration for later retrieval (it isn't displayed anywhere else). Best for a one-time or internal export you don't want visible on Synthesis.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FFWKHGJZHNFUCKpHprrLn%2Fcustom%20table%20export.png?alt=media&amp;token=ce3c521b-c90d-4a20-9d13-36d52ca9441b" alt="Custom Table Export page showing a table preview and the Table Builder controls."><figcaption><p>Build a Custom Table for immediate download from the Export page.</p></figcaption></figure>

* [**Dashboard Editor**](/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md) (as a Table card): the same builder, but the result lives on your Dashboard, updates as the nest changes, and displays on your shareable Synthesis page.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FM3uDpnAeOOSI6SskMmAV%2Fdashboard%20table.png?alt=media&amp;token=c4da098b-754e-4b65-ae2f-c9746bf9ab95" alt="Dashboard Editor showing a Table card with Custom Table Builder controls."><figcaption><p>Build a Custom Table as a Table card in Dashboard Editor.</p></figcaption></figure>

One functional difference exists between the two: the Export page offers an **Advanced** setting that splits columns under each root tag into separate workbook sheets on download (see "Advanced settings," below); Dashboard Editor's Table card doesn't offer this option.

Everything below applies equally in both places, except Advanced Settings, which is Export-page only. Watch the **Preview** as you build — it always reflects the exact structure your table will have once exported.

## Build Your Table

{% stepper %}
{% step %}

### Choose Your Table Type

The first decision is what each row represents — it determines every filter and column option that follows. Select your type from the **Table of:** dropdown.

If Meta-Analytical Extraction isn't configured, Study Arms and Interventions tables produce no rows at all rather than an error. If your extraction happened entirely in Tagging, use a Study table and add the relevant tags as columns instead of switching table types.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FRrvIP7Kz2AJT10bGkuvV%2Ftable%20of%20.png?alt=media&amp;token=85f62eda-4d7e-4148-b131-ced94b472dfb" alt="Table of dropdown showing Study, Study Arms, Interventions, and Tags table types."><figcaption><p>Select the table type that determines what each row represents.</p></figcaption></figure>

| Table type          | Each row is                                                 | Requires                             | Best for                                                                              |
| ------------------- | ----------------------------------------------------------- | ------------------------------------ | ------------------------------------------------------------------------------------- |
| **Study** (default) | One study                                                   | Nothing extra                        | Most tables — recommended starting point                                              |
| **Study Arms**      | One arm within a study (so one study may span several rows) | Completed Meta-Analytical Extraction | Exporting exact data elements per arm — the most common type for statistical analysis |
| **Interventions**   | One intervention                                            | Completed Meta-Analytical Extraction | A summary closest to Quantitative Synthesis's Summary view                            |
| **Tags**            | One tag (exports your tag hierarchy itself, not study data) | Nothing extra                        | Documenting hierarchy structure, depth, or how often tags were applied                |
| {% endstep %}       |                                                             |                                      |                                                                                       |

{% step %}

### Filter (Optional)

By default, a Custom Table includes every included study in the nest. Narrow it with the **Filter To** dropdown — available filters depend on your table type:

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FVH7tLSQ85kcZ27zhI3qx%2Ffilter%20table.png?alt=media&amp;token=21b77e00-6a30-419b-bf1f-051b7e8f7954" alt="Filter To dropdown in the Table Builder showing available filters for a Custom Table."><figcaption><p>Use Filter To to restrict the included studies in your table.</p></figcaption></figure>

| Table type    | Available filters                                                                                               |
| ------------- | --------------------------------------------------------------------------------------------------------------- |
| Study         | Publication date, time of retrieval, applied tags, full text status, related report family, related report type |
| Study Arms    | Everything available for Study, plus arms with a specific intervention and/or data element                      |
| Interventions | Studies with a specific intervention                                                                            |
| Tags          | Tags at or below a specific hierarchy level                                                                     |
| {% endstep %} |                                                                                                                 |

{% step %}

### Add Columns

Define columns from the **Columns** dropdown. Which options appear depends on your table type:

* **Bibliographic data** — Citation, Title, Year, Publication Date, Author(s), DOI, PubMed ID, article link, and more. Select **Citation** to put all reference information in a single cell, formatted in JAMA style. Select **Synthesis Link** to give each row a clickable link back to that study's page in your interactive Synthesis view — useful for keeping a downloaded table connected to the underlying evidence.
* **Full Text Status** — whether a full text has been imported for each study.
* **Tag** — tag names or excerpt text, at or below a chosen tag, or for one exact tag (see "Adding tag columns," below).
* **Arm data** — **Intervention** (the intervention applied to a cohort or arm) or **Arm Size** (total patients in a study or arm; requires Meta-Analytical Extraction for arms).
* **Data Element** — the exact quantitative value tied to a study arm or cohort, from Meta-Analytical Extraction. Categorical data elements can't be exported this way, since their structure doesn't fit a single column.
* **Tag Metadata** (Tags table only) — name, description, depth, and data element type.
* **Tag Statistics** (Tags table only) — Exact Frequency and/or Recursive Frequency (how often the tag, or any of its children, was applied).

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FKH7v1EtjMDWb5SWZHQzi%2Fcolumn%20table.png?alt=media&amp;token=50aa64d6-e5ab-4f3f-9b30-ed6e9f8d1abd" alt="Columns dropdown showing bibliographic data, full text status, tags, arm data, and data elements."><figcaption><p>Add bibliographic, tag, arm, or data element columns from the Columns dropdown.</p></figcaption></figure>

#### Adding Tag Columns

A tag column can show more than just the tag's name. Two independent toggles control what each cell displays:

|                  | Children off                                                                                                                                                             | Children on                                                                                                                    |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| **Contents on**  | Select a child tag → its name is the header; cells show that tag's annotation or excerpt text. Use for a specific child tag with content worth reading like a tag table. | Select a parent tag → its name is the header; cells list every applied child tag together with its annotation or excerpt text. |
| **Contents off** | Select a child tag → its name is the header; cells just show the tag name where it was applied. Useful as a yes/no indicator.                                            | Select a parent tag → its name is the header; cells list the applied child tags by name only, without content.                 |

Set both toggles before adding the column, or adjust them afterward from the two small icons on the column's pill: a lines icon for **Contents**, an asterisk icon for **Children** — an icon showing means that setting is on. You don't need to remove and re-add a column to change either setting.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2F07J6zfDAMKww9rKtOB7W%2Ftag%20columns.png?alt=media&amp;token=5bbc529b-f885-4c49-9437-f888352430cd" alt="Added tag column showing the Contents and Children controls on its column pill."><figcaption><p>Adjust Contents and Children for an added tag column from its column pill.</p></figcaption></figure>

#### Combining Tag Tables

If you've extracted data into tag tables, you can pull individual tags or an entire table's contents into your Custom Table — from the Columns dropdown, with Contents on and Children off, tags with an associated table show a table icon; select one, or choose **All Table Contents** to bring in everything at once.

When more than one tag table is added, combine them one of two ways:

* **Concatenation** (default, no setup needed) — tables display side by side exactly as filled out, adding rows for a study as needed. Matching column headers aren't merged; if two tables each have an "Arm" column, both appear separately. Index Tables can only be combined this way.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FKDpzFHr35I9V14kTq11f%2Fconcatenate.png?alt=media&amp;token=c14dd44c-21d1-47b5-8c8c-d7ea0fc16113" alt="Custom Table preview showing tag tables combined through concatenation, with tables displayed side by side."><figcaption><p>Concatenation keeps tag tables separate and displays them side by side.</p></figcaption></figure>

* **Joins** — merges columns with matching names automatically. Select **Combine Tables: Join**, and Nested Knowledge attempts the match — for example, two tables that each have an "Arm" column are combined into one. Since joins are assigned automatically, they can be wrong: select the icon between the listed tag tables, select **X** on any incorrect pairing, and manually join the correct columns from the same panel.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2F132AKfndsMuOsKiMD06U%2Fjoins.png?alt=media&amp;token=d1f40ded-15d3-4c04-a95d-d80df2b0efa9" alt="Join settings panel showing matched columns between two tag tables."><figcaption><p>Review and adjust the column pairings when joining tag tables.</p></figcaption></figure>
{% endstep %}

{% step %}

### Sort Studies (Optional)

Control row order by sorting on bibliographic data, meta-analytical extraction (where applicable), or assigned related report families.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FHP1CV22CAmUL1zyhhbKv%2Fsort%20by%20table.png?alt=media&amp;token=edfa363d-77b7-47e4-b435-0a38922ea5fd" alt="Sort controls in the Table Builder showing selected fields and sort direction."><figcaption><p>Set the fields and direction that determine the table's row order.</p></figcaption></figure>
{% endstep %}

{% step %}

### Reorder Or Remove Columns

Drag a column's pill to reorder it; select the **X** on a pill to remove that column from the table.
{% endstep %}

{% step %}

### Wrap Cells/Headers (Dashboard Only)

For greater visibility of data in the configured table in your Dashboard card, toggle on Wrap Cells and/or Headers.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FHCFk81DhcuMNsln2tpSF%2Fwrap%20cells%20dashboard.png?alt=media&amp;token=84732671-3d84-48d7-b7cb-73e6e319c72b" alt="Dashboard Table card settings showing the Wrap Cells and Wrap Headers toggles."><figcaption><p>Use Wrap Cells and Wrap Headers to show more table content in a Dashboard card.</p></figcaption></figure>
{% endstep %}

{% step %}

### Save Table

The Table Builder resets when the page refreshes, so save any configuration you've invested time in: add a name and select **Save**. Return later and open **Saved Tables** to auto-populate the builder from that configuration.

In **Dashboard Editor**, select **Save**. The card saves and updates automatically in your Dashboard.
{% endstep %}
{% endstepper %}

### Advanced Settings (Export Page Only)

Before downloading, check the **Advanced** toggle. By default, when your table includes tag columns organized under separate root tags, each root tag's columns export to their own sheet in the workbook, named for that root tag — useful for organizing a large dataset. Turn this off to keep every column in a single sheet instead.

Once configured, select **Download**.

### FAQs

<details>

<summary>I added a column, but it's blank in the preview/after I save — why?</summary>

This is usually one of two things: the underlying data isn't there for that study (the tag wasn't applied, or the bibliographic field is missing from the record), or — for tag columns specifically — you selected a parent tag without turning **Children** on. Without it, the column only looks for the parent tag itself, which is often blank; turning Children on shows the parent's applied child tags instead. This works like filtering in Study Inspector, except here the setting isn't turned on for you by default — you need to select it yourself.

</details>

<details>

<summary>Can I reuse a table configuration I've built before?</summary>

Yes — save it when building, and retrieve it from **Saved Tables** the next time you're on this page.

</details>

<details>

<summary>I need this exact table to update automatically — can I convert it?</summary>

Not automatically from here. Rebuild the same table type, filters, and columns using the Table Builder inside [Dashboard Editor](/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md) instead.

</details>

<details>

<summary>Which table type should I use if I extracted my data through Tagging rather than Meta-Analytical Extraction?</summary>

Use a **Study** table, and add the relevant tags as columns — Study Arms and Interventions tables only populate from Meta-Analytical Extraction.

</details>

### Next Steps

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-table-columns">:table-columns:</i><br><strong>Dashboard Editor</strong></td><td>Build a living version of this table.</td><td><a href="/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md">Dashboard Editor</a></td></tr><tr><td><i class="fa-file-arrow-down">:file-arrow-down:</i><br><strong>Download from Inspector</strong></td><td>Export data for all studies or filtered study sets.</td><td><a href="/review-workflow/study-inspector/download-from-inspector.md">Download from Inspector</a></td></tr><tr><td><i class="fa-file-lines">:file-lines:</i><br><strong>CER Builder</strong></td><td>Export Search and Screening documentation for a CER submission.</td><td><a href="/review-workflow/exports/cer-builder.md">CER Builder</a></td></tr></tbody></table>


---

# 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.nested-knowledge.com/review-workflow/exports/custom-tables.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.
