Page 7347 "Locations with Warehouse List"
Base Application · Microsoft.Warehouse.Structure
Across versions
- BC23-30present
Neighbourhood 8 connected objects and pages
Base Application · Microsoft.Warehouse.Structure · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Locations with Warehouse List |
| SourceTable | Location |
| 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 | Code | Code | Specifies a location code for the warehouse or distribution center where your items are handled and stored before being sold. |
| Name | Name | Specifies the name or address of the location. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Line | Zones | View or edit information about zones that you use in your warehouse to structure your bins under zones. | Page 7300 “Zones” |
| Bins | View or edit information about zones that you use in your warehouse to hold items. | Page 7302 “Bins” |
Triggers
OnOpenPage
Relations
- card page Page 5703 “Location Card”
- source table Table 14 “Location”
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)
Called by
- Table 7316 “Warehouse Receipt Header” (1 call:
LookupLocation → (object)) - Table 7320 “Warehouse Shipment Header” (1 call:
LookupLocation → (object)) - Table 7331 “Whse. Internal Put-away Header” (1 call:
LookupLocation → (object)) - Table 7333 “Whse. Internal Pick Header” (1 call:
LookupLocation → (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: "Locations with Warehouse List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.