Nested repeats
Use Wappler’s Form Repeat and selection-aware Properties flow to understand how nested repeated rows get their data scope.
Nested repeated rows
This tour opens a Form Repeat example so you can inspect the real Wappler controls that define a repeated row source and the row-level scope that nested bindings depend on.
The repeated row container starts in App Structure
A nested repeat starts with a parent component that owns the repeated row block. This Form Repeat container is that outer structure, and selecting it is what exposes the row source and constraints in Properties.
The repeated source lives inside the Properties workflow
Start with the wider Properties area before zooming into the row-source field. That context matters because nested repeat setup is a mix of structure selection and property-level source binding.
The Items source defines the outer collection
This Items property is the source collection for the repeated rows. Each row created from this collection gets its own local scope, which is the foundation nested repeat bindings build on.
Selection controls the row scope you are editing
Nested repeated bindings only make sense when you are editing the right repeated node. In Wappler, that means selecting the repeated container or its child row in App Structure before opening pickers or changing bindings.
Continue with the deeper repeat tours
This topic focused on the Wappler UI surfaces that control repeated row scope and repeated data sources. Continue with Form Repeat for the full repeated-row workflow, or open Conditional display & repeating lists for the broader repeat model.
