---
title: "Joining from Document to Dataset Fields"
slug: "joining-from-document-to-dataset-fields"
status: "new"
updated: 2026-07-21T20:22:24Z
published: 2026-07-21T20:22:24Z
canonical: "knowledge.technolutions.net/joining-from-document-to-dataset-fields"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Joining from Document to Dataset Fields

Use an independent subquery join when a document export query needs values from an organization contact or another dataset record and no standard Document base join is available. This pattern is commonly used when custom document file names or index files need dataset-scoped values.

> [!TIP]
> ⭐ Get Inspired
> 
> This article was adapted from [a post by Technolutions staff](https://community.technolutions.net/get-inspired/post/joining-from-document-to-organization-contact-dataset-fields-yH5QOPKERHvdxY7) in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? [Let us know](https://community.technolutions.net/get-inspired/new?post_type=gnHx7As1gZ8r6Ld)!

## When to use this

- The query base is Document or Document Export.
- The needed value lives on an organization contact, standard dataset record, or custom dataset record.
- The document has a one-to-one relationship with the dataset row you need to return.

> [!WARNING]
> 📝 Note
> 
> This article describes a query-building pattern. Confirm the relevant GUID relationship in your own query before using the joined values in production exports.

## Add an independent subquery join

1. Open the document export query.
2. In the joins section, select the subquery join option.
3. Configure the join with these settings:

- **Name:** Enter a clear name, such as **Organization Contact**.
- **Type:** Independent Subquery.
- **Category:** Records.
- **Base:** Select **Organization Contacts**, or select the custom dataset base you need.

## Connect the independent subquery to the document

1. Inside the independent subquery join, add a subquery filter.
2. Configure the filter as a dependent subquery.
3. Set the aggregate to **Comparison**.
4. Set the operator to **=**.
5. Add one export for the document record GUID.
6. Add one export for the GUID from the independent subquery base.
7. Select those two exports as **Field 1** and **Field 2** in the comparison filter.
8. Save the filter and the join.

After the join is saved, the query can use fields from the organization contact or dataset row as exports, filters, and additional joins.

## Use the joined values

Once the independent subquery join is available, you can use the joined dataset fields for tasks such as:

- Adding dataset values to an index file.
- Building a custom `pdf:file` export for document file names.
- Filtering the document export by values on the related dataset record.

## Adapt the pattern for custom datasets

To join from a document to a custom dataset, use the same structure but select the custom dataset as the independent subquery base. Then compare the document record GUID to the dataset row GUID or other stable relationship value that connects the two records.

## Test before scheduling the export

1. Run the query for a small, known set of documents.
2. Confirm that each returned document is associated with the expected organization contact or dataset row.
3. Confirm that the joined values are populated in the file name or index exports.
4. Only then configure or resume a scheduled export.

## Related articles

- [Building a Document Export Query](https://knowledge.technolutions.net/docs/en/creating-a-document-export-query-with-configurable-joins)
- [Customizing Exported Document File Names](https://knowledge.technolutions.net/docs/en/customizing-the-document-file-name-in-a-document-export-query)
- [Migrating to Configurable Joins](https://knowledge.technolutions.net/docs/en/migrating-to-configurable-joins)