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

Page 30042 "APIV2 - Purchase Invoices"

APIV2 · Microsoft.API.V2

Across versions

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

Neighbourhood 11 connected objects and pages

Table 5477 "Purch. Inv. Entity Aggregate" (relates to)Purch. Inv. Entity AggregateCodeunit 5529 "Purch. Inv. Aggregator" (calls, 8 links)Purch. Inv. AggregatorCodeunit 1320 "Lines Instruction Mgt." (calls)Lines Instruction Mgt.Codeunit 5465 "Graph Mgt - General Tools" (calls)Graph Mgt - General ToolsCodeunit 66 "Purch - Calc Disc. By Type" (calls)Purch - Calc Disc. By TypeCreate purchaseInvoices (Learn pages)Create purchaseInvoicesDelete purchaseInvoices (Learn pages)Delete purchaseInvoicesGet purchaseInvoice pdfDocument (Learn pages)Get purchaseInvoice pdfDocum…Get purchaseInvoices (Learn pages)Get purchaseInvoicespurchaseInvoice resource type (Learn pages)purchaseInvoice resource typeUpdate purchaseInvoices (Learn pages)Update purchaseInvoices

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 Purch. Inv. Entity Aggregate
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 Id —
No. No. —
Posting Date Posting Date —
Invoice Date Document Date —
Due Date Due Date —
Vendor Invoice No. Vendor Invoice No. —
Vendor Id Vendor Id —
Vendor No. Buy-from Vendor No. —
Vendor Name Buy-from Vendor Name —
Pay-To Name Pay-to Name —
Pay-To Contact Pay-to Contact —
Pay-To Vendor Id Pay-to Vendor Id —
Pay-To Vendor No. Pay-to Vendor No. —
Ship-To Name Ship-to Name —
Ship-To Contact Ship-to Contact —
Buy-from Address Line 1 Buy-from Address —
Buy-from Address Line 2 Buy-from Address 2 —
Buy-from City Buy-from City —
Buy-from Country/Region Code Buy-from Country/Region Code —
Buy-from State Buy-from County —
Buy-from Post Code Buy-from Post Code —
Ship-to Address Line 1 Ship-to Address —
Ship-to Address Line 2 Ship-to Address 2 —
Ship-to City Ship-to City —
Ship-to Country/Region Code Ship-to Country/Region Code —
Ship-to State Ship-to County —
Ship-to Post Code Ship-to Post Code —
Pay To Address Line 1 Pay-to Address —
Pay To Address Line 2 Pay-to Address 2 —
Pay To City Pay-to City —
Pay To Country/Region Code Pay-to Country/Region Code —
Pay To State Pay-to County —
Pay To Post Code Pay-to Post Code —
Shortcut Dimension 1 Code Shortcut Dimension 1 Code —
Shortcut Dimension 2 Code Shortcut Dimension 2 Code —
Currency Id Currency Id —
Currency Code CurrencyCodeTxt —
Order Id Order Id —
Order No. Order No. —
Purchaser Purchaser Code —
Prices Include Tax Prices Including VAT —
Dimension Set Lines part Page 30022 “APIV2 - Dimension Set Lines” —
Lines part Page 30047 “APIV2 - Purchase Invoice Lines” —
PDF Document part Page 30056 “APIV2 - PDF Document” —
Discount Amount Invoice Discount Amount —
Discount Applied Before Tax Discount Applied Before Tax —
Total Amount Excluding Tax Amount —
Total Tax Amount Total Tax Amount —
Total Amount Including Tax Amount Including VAT —
Status Status —
Last Modified Date Rec.SystemModifiedAt —
Attachments part Page 30039 “APIV2 - Attachments” —
Document Attachments part Page 30080 “APIV2 - Document Attachments” —

Procedures

  • Post(var ActionContext: WebServiceActionContext)

Plus 9 local procedures.

Triggers

OnAfterGetRecord, OnDeleteRecord, OnInsertRecord, OnModifyRecord, OnNewRecord, OnOpenPage

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 - Purchase Invoices"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 7 sources