Page 11 "Shipment Methods"
Base Application · Microsoft.Foundation.Shipping
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Foundation.Shipping · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Shipment Methods |
| SourceTable | Shipment Method |
| PageType | List |
| UsageCategory | Administration |
| 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 a code for the shipment method. from the table field |
| Description | Description | Specifies a description of the shipment method. from the table field | |
| Coupled to Dataverse | CDSIsCoupledToRecord |
Specifies that the shipment method is coupled to a freight term in Dataverse. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Translation | Describe the shipment method in different languages. The translated descriptions appear on quotes, orders, invoices, and credit memos, based on the shipment method code and the language code on the document. | Page 757 “Shipment Method Translations” |
| Dataverse | Synchronize | Send or get updated data to or from Dataverse. | |
| Coupling | Set Up Coupling | Create or modify the coupling to a Dataverse Freight Term. | |
| Match-Based Coupling | Couple shipment methods in Dataverse based on criteria. | ||
| Delete Coupling | Delete the coupling to a Dataverse Freight Term. | ||
| Dataverse | Synchronization Log | View integration synchronization jobs for the shipment method table. |
Triggers
OnAfterGetRecord, OnOpenPage
Relations
- source table Table 10 “Shipment Method”
Pages and codeunits on this table
- Table 10 “Shipment Method” (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 5330 “CRM Integration Management” (1 call:
OnOpenPage → IsCDSIntegrationEnabled)
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: "Shipment Methods"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.