Page 8620 "Config. Template List"
Base Application · System.IO
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · System.IO · captioned “Configuration Templates” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Configuration Templates |
| SourceTable | Config. Template Header |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | Basic, Suite |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Code | Code | Specifies the code of the data template. |
| Description | Description | Specifies a description of the data template. | |
| Table ID | Table ID | Specifies the ID of the table on which the data template is based. | |
| Table Name | Table Name | Specifies the name of the table on which the data template is based. |
Relations
- card page Page 8618 “Config. Template Header”
- source table Table 8618 “Config. Template Header”
Pages and codeunits on this table
- Table 8618 “Config. Template Header” (lookup page)
Called by
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 8612 “Config. Template Management” (1 call:
UpdateFromTemplateSelection → (object))
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Config. Template List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.