Page 823 "Name/Value Lookup"
Base Application · Microsoft.Utilities
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Utilities · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Name/Value Lookup |
| SourceTable | Name/Value Buffer |
| PageType | List |
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 |
|---|---|---|---|
| Control1000 | Name | Name | Specifies the name. from the table field |
| Value | Value | Specifies the value. from the table field |
Procedures
AddItem(ItemName: Text[250]; ItemValue: Text[250])
Relations
- source table Table 823 “Name/Value Buffer”
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.
- Table 370 “Excel Buffer” (1 call:
SelectSheetsNameStream → (object))
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: "Name/Value Lookup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.