pagePurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Page 9100 "Purchase Line FactBox"

Base Application · Microsoft.Purchases.Document

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 39 "Purchase Line" (relates to)Purchase LinePage 30 "Item Card" (calls)Item Card

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.

Base Application · Microsoft.Purchases.Document · captioned “Purchase Line Details” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Purchase Line Details
SourceTable Purchase Line
PageType CardPart

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
Content Item No. No. Specifies the number of a general ledger account, item, resource, additional cost, or fixed asset, depending on the contents of the Type field.
Availability PurchInfoPaneMgt.CalcAvailability(Rec) Specifies how many units of the item on the purchase line are available.
Purchase Prices StrSubstNo('%1', PurchInfoPaneMgt.CalcNoOfPurchasePrices(Rec)) Specifies how many special prices your vendor grants you for the purchase line. Choose the value to see the special purchase prices.
Purchase Line Discounts StrSubstNo('%1', PurchInfoPaneMgt.CalcNoOfPurchLineDisc(Rec)) Specifies how many special discounts your vendor grants you for the purchase line. Choose the value to see the purchase line discounts.
Attachments Documents Attached Doc Count Specifies the number of attachments. from the table field

Procedures

  • ShowDetails() (protected)

Triggers

OnAfterGetCurrRecord

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.

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

Evidence 1 sources