---
title: "Nesting a Data Grid in a Data Repeater"
slug: "nesting-a-data-grid-in-a-data-repeater"
updated: 2025-04-23T18:08:13Z
published: 2025-04-23T18:08:13Z
canonical: "documentation.decisions.com/nesting-a-data-grid-in-a-data-repeater"
---

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

# Nesting a Data Grid in a Data Repeater

Example Lab ArticleWhile Example Lab projects are resources for public use, articles and assets are not actively maintained. Screenshots and features are from the specified version below. These references may become dated as new versions are released.

---

## Overview

| ## Example Lab Details |
| --- |
| **Version** | 7.6.0 |
| **Root Folder** | Example Lab - Nesting a Data Grid in a Data Repeater |
| **Modules** | None |
| **Dependencies** | None |

This Example Lab demonstrates how to nest a data grid in a data repeater for eliciting hierarchical data from the end user.

---

## Explanation

In this example, the Form demonstrates how to nest a data grid in a data repeater to gather layered data.

Open the Flow in the project file below and click on the Form. Under "DataRep" in Inputs, the person Defined Data Structure pairs with the car Defined Data Structure to populate this project with sample data upon running the Flow. If wishing to add more, clicking the Add button provides prompts for data prompts for both Defined Data Structures.

Click on the Edit Source button at the top of the Properties menu to open the data repeater editor. Click on the data grid to view its configuration. The Column Information populates the data grid with the provided column names: color, model, and year in this example. Under Input Data, the Data Name selected the car Defined Data Structured found within the Form hence name "Form.Car" in this example. PickTypes chooses "PickType" then for Type, the car Defined Data Structure is also selected.

To allow the end user to edit items within the lines, the "InlineEdit" Grid Mode is selected under Output Data. The Data Name under Output Data matches the Input Data Data Name: "Form.Car" so the data entered by the end user may travel in the Flow after the end user submits the Form.

Reference Articles[Create Data Repeater Form Control](https://documentation.decisions.com/docs/creating-data-repeaters)  
[Editing Data Grid Items Inline](https://documentation.decisions.com/docs/editing-data-grid-items-inline)

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-09-01_11h03_46.png)

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-09-01_11h06_44.png)

---

## Project Download

The examples attached were developed to be instructional and were not developed as officially supported components. For more information or to engage our service team to develop fully supported, production quality solutions, please contact services@decisions.com. Import the project below to a Decisions environment on v7.6.0 or later using our [Importing/Exporting](https://documentation.decisions.com/docs/exporting-and-importing-overview) article.  
  
[ExampleLab[NestingADataGridInADataRepeaterSample].zip](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/ExampleLab%5BNestingADataGridInADataRepeaterSample%5D.zip)

---