pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 30024 "APIV2 - Shipment Methods"

APIV2 · Microsoft.API.V2

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 7 connected objects and pages

Table 10 "Shipment Method" (relates to)Shipment MethodCodeunit 5465 "Graph Mgt - General Tools" (calls)Graph Mgt - General ToolsCREATE shipmentMethods (Learn pages)CREATE shipmentMethodsDELETE shipmentMethods (Learn pages)DELETE shipmentMethodsGET shipmentMethods (Learn pages)GET shipmentMethodsshipmentMethod resource type (Learn pages)shipmentMethod resource typeUPDATE shipmentMethod (Learn pages)UPDATE shipmentMethod

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

APIV2 · Microsoft.API.V2 · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Extensible false
SourceTable Shipment Method
PageType API

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
Group Id Rec.SystemId —
Code Code Specifies a code for the shipment method. from the table field
Display Name Description Specifies a description of the shipment method. from the table field
Last Modified Date Rec.SystemModifiedAt —

Procedures

1 local procedures, no public ones.

Triggers

OnInsertRecord, OnModifyRecord

Relations

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.

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: "APIV2 - Shipment Methods"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 6 sources