---
title: "Map Family Relationships - Review Manager"
slug: "map-family-relationships-review-manager"
updated: 2026-03-12T13:36:11Z
published: 2026-03-12T13:36:11Z
---

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

# Map Family Relationships - Review Manager

When importing data using a DAT/CSV load file in Reveal Review Manager, document family relationships are defined in the [***Field Mapping***](https://review-help.revealdata.com/en/Mapping-Import-Fields.html) process. The following steps set out the requirements and considerations for applying this process.

## Import Data

1. Import Mapping with Begin Number and Item ID
  1. When mapping fields, the document **Begin Number** (i.e., the Control Number or Unique Identifier) should be mapped to the Reveal **Begin Number** (this is known as **BEGDOC** in the underlying database table).
  2. The **Item ID** (known as **ITEMID** in the database) should be selected with the option *“Auto Generated”.*

> [!NOTE]
> Note
> 
> Do not map **Item ID** to a field.
    1. The **Item ID** is auto generated with a sequential number starting at 1 for each project.
2. Import Mapping and Begin Number Attach.
  1. To create family relationships, **Begin Number Attach**(known as **BEGATTACH** in the database) must be in the initial documents import, or overlaid with the **BEGDOC** field.
  2. The **Begin Number Attach** field must correspond to the parent document’s **Begin Number** across the entire set.****It must therefore be mapped to the **BEGATTACH** field.
    1. The **BEGATTACH** is populated across attachments (also known as children) with the parent document’s **BEGDOC**.
    2. The parent documents will also have **BEGATTACH** populated.

![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/173%20-%2001%20-%20Mapping%20Family%20Relationships01-1.png)
  3. This will set the **PARENT_ITEMID**, **EMT_FAMILYID**, **FAMILY_RELATIONSHIP**, and **Has Family** metadata fields based on **BEGATTACH** for all Import Batches.
  4. The display name for **EMT_FAMILYID** is **BD EMT FamilyID**.
  5. The display name for **FAMILY_RELATIONSHIP** is **Family Relationship**.
  6. **EMT_FAMILYID** is ***NULL*** for any docs that do not have children.

> [!NOTE]
> Note
> 
> If **Begin Number Attach** does not match an existing **Begin Number**, an error will be thrown for the **Parent ID** field.
3. Once data has been imported and any Natives/Text has stored successfully, indexing may be initiated, including the Document Metadata Index.
4. The Family icon and the Family relationship panel should now display for all applicable documents.

## Update Data (Creating or Updating Families After Import)

1. Ensure at minimum that you have the **Begin Number** and the **Begin Number Attach**
2. In Review Manager, open **Import > Documents**.
3. Select the Project to be updated.
4. Select **Update Data**.
5. Use a mapping that has the “**Begin Number**” and “**Begin Number Attach**” fields.
6. Choose the load file.
7. Select **Import Data** to begin (using ***Test Mode Only*** first is recommended to check for errors).

Once the values have been updated successfully, the family relationships must be rebuilt from the **Reveal Web interface**.

## Rebuild Family Relationships

1. Open the **Reveal Web interface**.
2. Navigate to the relevant **Project**.
3. Go to **Project Admin**.
4. Select **Rebuild Document Data**.
5. Click on **Rebuild** to run the process.

![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image-Q9M9GKJI.png)

The system will rebuild document families and populate **Parent ID** for child documents using the parent document’s **Item ID**

> [!NOTE]
> Note
> 
> The process may take some time depending on the project size, as the system updates database functions that support family information such as the **Family Member Grid icon**, **Family Relationship panel**, and **search functionality**.

Document metadata indexing is now automatically handled by the system after rebuilding document data. Manual indexing is no longer required.

## Related

- [Security Policy for Files Uploaded](/security-policy-for-files-uploaded.md)
- [Reveal 2024 Project Admin Sidebar](/reveal-2024-project-admin-sidebar.md)
- [Reveal - Supported File Formats for Review](/reveal-supported-file-formats-for-review.md)
- [Manage Default Project Settings](/manage-default-project-settings.md)
- [Tag Validation Rules - Set, Test, and Use](/tag-validation-rules-set-test-and-use.md)