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

Page 30048 "APIV2 - Cust Financial Details"

APIV2 · Microsoft.API.V2

Across versions

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

Neighbourhood 3 connected objects and pages

Table 18 "Customer" (relates to)CustomercustomerFinancialDetail resource type (Learn pages)customerFinancialDetail reso…GET customerFinancialDetails (Learn pages)GET customerFinancialDetails

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 Customer
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 —
No. No. Specifies the number of the customer. The field is either filled automatically from a defined number series, or you enter the number manually because you have enabled manual number entry in the number-series setup. from the table field
Balance Balance (LCY) Specifies the total amount the customer owes you, or you owe them, based on all sales and credits for the customer. A positive amount means they owe you, and a negative amount means you owe them. The amount isn’t necessarily due today though. The customer’s payment terms determine due dates. Select … from the table field
Total Sales Excluding Tax Sales (LCY) Specifies the total net amount of sales to the customer in LCY. from the table field
Overdue Amount Balance Due (LCY) Specifies the total amount that’s due from the customer as of today. Consider using reminders to minimize late payments and optimize cashflow. from the table field
Last Modified Date Rec.SystemModifiedAt —

Triggers

OnAfterGetRecord

Relations

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

Evidence 3 sources