Create the child before attaching it
A Submodule is generated independently, then attached to one or more parent modules. Define its own primary key, parent-link field and line fields before selecting it in the parent.
Runtime tenant submodules need the company context expected by generated access and lookup behaviour. The builder and generator manage the supported pattern; do not add an unrelated manual CompanyID merely to satisfy a draft.
Relationship settings
Select the existing Submodule and configure the parent/child relationship with supported attachment fields.
- Relationship name: a user-friendly name for the line-item section.
- Parent field: the parent module primary key.
- Child field: the foreign-key placeholder stored in each child row.
- Minimum rows: zero for optional lines or a positive number when at least one row is required.
- Maximum rows: an optional safety or business limit.
Place the child in the form
Attachment alone does not determine visual position. Open Form Designer and place the entire child section as its own layout row. The generated form renders the child table at that position.
- Use the Submodule line-item layout for the child itself.
- Do not place individual child fields in the parent layout.
- Keep sufficient spacing after the child table before the next parent row.
- Test adding, editing and removing rows in both parent Create and Edit pages.
Downstream use
An attached child can supply line-level values to voucher posting, stock movement, GST mapping and Print Studio tables. Every downstream configuration must reference the selected submodule and verified child fields.
The submodule definition may be reused, but each parent record owns its own child rows through the configured parent/child key relationship.