Parent-Child Field Links
This page lets you map fields between a parent tool and a child tool in the same tool configuration.
Page type: List Source table:
Tool Config LinkObject:Page 72778340 "SA Tool Config Links QUA"—Page.72778340.SAToolConfigLinks.al
This page lets you map fields between a parent tool and a child tool in the same tool configuration. When the agent creates a child record (for example, a sales line), the system automatically copies the value from the parent field into the matching child field — so the agent does not need to repeat the parent key. You can add multiple rows to support compound keys (for example, both Document Type and Document No.).
In plain terms
This is how you teach the agent the header → lines relationship between two tools. When it creates the header (a sales order) and then the lines, the key has to carry over so the lines attach to the right document.
It works just like the Document No. flowing from a Sales Header to its Sales Lines: you wouldn't expect a user to retype the document number on every line, and the AI shouldn't have to either. These links copy the parent key into each child record automatically, so "create the order and its lines" wires up correctly. Add one row per key field (e.g. both Document Type and Document No.) for compound keys.
How to open it
- Parent Links action on the Agent Tool Configuration card (Available Tools subpage), with a tool row selected that has a Parent Object ID set. The action is only enabled when a parent is configured.
Fields
Lines
| Field | Type | Description |
|---|---|---|
| Parent Field Name | Text[80] | The field on the parent table whose value identifies the parent record (e.g. "No." on Sales Header). A lookup lets you browse fields on the parent table. |
| Child Field Name | Text[80] | The field on this (child) table that links to the parent (e.g. "Document No." on Sales Line). Auto-filled during record creation. A lookup lets you browse fields on the child table. |
Parent Field No. and Child Field No. are hidden from the list by default (
Visible = false). They store the BC field numbers and are filled automatically when you pick a field from the lookup.
Related pages
- Agent Tool Configuration — parent page that opens this via Parent Links
- Tool Field Defaults — per-field rules for the same tool
Notes
- Before you can open this page, the child tool must have a Parent Object ID set in the Available Tools list.
- Use the field lookup (the assist-edit button in the Parent Field Name and Child Field Name cells) to browse available fields. The lookup automatically filters to the correct parent or child table.
- If you clear Parent Object ID on a tool, all link rows for that tool are deleted automatically.
- Multiple rows are needed for compound primary keys — add one row per field pair.