Page 7704 "Functions"
Base Application · Microsoft.Warehouse.ADCS
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Warehouse.ADCS · captioned “Miniform Functions Group” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Miniform Functions Group |
| SourceTable | Miniform Function Group |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | ADCS |
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 that represents the function used on the handheld device. from the table field |
| Description | Description | Specifies a short description of what the function is or how it functions. from the table field | |
| KeyDef | KeyDef | Specifies the key that will trigger the function. from the table field |
Relations
- source table Table 7702 “Miniform Function Group”
Pages and codeunits on this table
- Table 7702 “Miniform Function Group” (lookup page)
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). 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: "Functions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.