Page 7346 "Worksheet Names List"
Base Application · Microsoft.Warehouse.Worksheet
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Warehouse.Worksheet · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Worksheet Names List |
| SourceTable | Whse. Worksheet Name |
| 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 |
|---|---|---|---|
| Control1 | Name | Name | Specifies the name you enter for the worksheet. from the table field |
| Location Code | Location Code | Specifies the location code of the warehouse the worksheet should be used for. from the table field | |
| Description | Description | Specifies the description for the worksheet. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Edit Worksheet | Open the related worksheet. |
Triggers
OnInit, OnOpenPage
Relations
- source table Table 7327 “Whse. Worksheet Name”
Pages and codeunits on this table
- Table 7327 “Whse. Worksheet Name” (lookup page)
Calls
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 7302 “WMS Management” (1 call:
OnOpenPage → GetWarehouseEmployeeLocationFilter)
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: "Worksheet Names List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.