Nested Repeater Feasibility in Forms

Yes, nesting a Repeater inside another Repeater is technically possible—but not recommended. It often leads to slower rendering, complex data binding, and maintainability headaches, especially as the data grows.

A better approach would be to use a Data Repeater to represent each student and nest an Advanced Data Grid inside the repeater to manage that student’s subjects.

Here’s a working example of how that looks:

• Each Repeater row holds one student.
• Inside each row, an Advanced Data Grid displays and manages that student's subjects.
• You can place Add/Remove buttons for both students (at the top level) and for subjects (inside each student section).
• Users can add or remove both students and their subjects all in one place.

When to use this:

• Works well for smaller datasets (e.g., 10–15 students, each with 3–5 subjects).
• Great for quick edits and bulk input where switching to sub-dialogs feels excessive.

When to avoid it:

• If the subject lists get long or if you need complex validation per subject, consider moving the subject editing into a sub-dialog instead. It improves clarity and performance.

Please refer to https://documentation.decisions.com/projects/docs/nesting-a-data-grid-in-a-data-repeater