Page 30030 "APIV2 - Units of Measure"
APIV2 · Microsoft.API.V2
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 7 connected objects and pages
APIV2 · Microsoft.API.V2 · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | Unit of Measure |
| 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 unit of measure, which you can select on item and resource cards from where it is copied to. from the table field | |
| Display Name | Description | Specifies a description of the unit of measure. from the table field | |
| International Standard Code | International Standard Code | Specifies the unit of measure code expressed according to the UNECERec20 standard in connection with electronic sending of sales documents. For example, when sending sales documents through the PEPPOL service, the value in this field is used to populate the UnitCode element in the Product group. from the table field | |
| Symbol | Symbol | — | |
| Last Modified Date | Rec.SystemModifiedAt |
— |
Procedures
1 local procedures, no public ones.
Triggers
OnInsertRecord
Relations
- source table Table 204 “Unit of Measure”
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 5465 “Graph Mgt - General Tools” (1 call:
OnInsertRecord → ProcessNewRecordFromAPI)
Documented on Microsoft Learn
- CREATE unitOfMeasures
- DELETE unitOfMeasures
- GET unitOfMeasures
- UPDATE unitOfMeasures
- unitOfMeasure resource type
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 - Units of Measure"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.