Page 30073 "APIV2 - Apply Vendor Entries"
APIV2 · Microsoft.API.V2
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 5 connected objects and pages
APIV2 · Microsoft.API.V2 · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | Vendor Ledger Entry Buffer |
| 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 |
|---|---|---|---|
| GroupName | Id | Rec.SystemId |
— |
| Applied | Applied |
— | |
| Applies-to Id | Applies-to ID | — | |
| Posting Date | Posting Date | — | |
| Document Type | Document Type | — | |
| Document No. | Document No. | — | |
| External Document No. | External Document No. | — | |
| Vendor No. | Vendor No. | — | |
| Vendor Name | Vendor Name | — | |
| Description | Description | — | |
| Remaining Amount | Remaining Amount | — | |
| Last Modified Date | Rec.SystemModifiedAt |
— |
Procedures
1 local procedures, no public ones.
Triggers
OnFindRecord, OnAfterGetRecord, OnModifyRecord
Relations
- source table Table 2250 “Vendor Ledger Entry Buffer”
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 225 “Gen. Jnl.-Apply” (2 calls:
OnModifyRecord → ApplyVendorLedgerEntryAPI,OnModifyRecord → SetVendApplIdAPI)
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 - Apply Vendor Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.