Repeat the Children of a Container — Reference

Keep one wrapper element and render its child template for every data item.

Before you begin

• An App Connect page. Use a small known data set when verifying data binding or repetition.

Repeat the Children of a Container

Keep one wrapper element and render its child template for every data item.

Properties, data and actions

Part	Meaning
ID	The repeat component identifier, for example productRows.
Expression	The collection to render, such as products.value or a Server Connect query array. The runtime supports arrays, objects and numeric counts; an array of records is the clearest starting point for data tables.
Unique Key	A stable unique field name in each record, such as id. It helps reconcile keyed items when order/data changes. Missing or duplicate keys defeat that identity assumption; do not use a non-unique product name.
Item scope	Within each rendered child template, the current record’s fields are directly available. $value contains the item, $index is zero-based and $key identifies its source key/index.
items data	The repeat’s exposed items are its current normalized item data. This is distinct from writing records back to the original server source.
update / updated events	Describe repeat updates. Avoid using an update handler to cause an unconditional cycle on the same collection.

Worked example

Use one tbody with ID productRows, Repeat Children and Expression products.value. Keep one template row inside it and bind its name cell to name. With Notebook and Pencil records, the table should show two different body rows while its heading appears once.

Behavior and limits

Children are repeated, not the wrapper. Every template child is copied for each item, so extra sample rows produce extra output. Keep static repeated IDs out of child markup or bind them uniquely. A page repeat is separate from a Server Connect Repeat that executes server steps.

Build the surrounding page flow

Use a practical App Connect guide when you need the surrounding page, input or server-data workflow.

Check your result

You can use the component’s actual data path, configure its controls and verify the example’s reactive behavior.