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

Page 9093 "Vendor Details FactBox"

Base Application · Microsoft.Purchases.Vendor

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 23 "Vendor" (relates to)VendorPage 26 "Vendor Card" (calls)Vendor 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.Vendor · captioned “Vendor Details” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Vendor Details
SourceTable Vendor
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 Vendor No. No. Specifies the number of the vendor. 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
Name Name Specifies the vendor’s name.
Phone No. Phone No. Specifies the vendor’s telephone number. from the table field
E-Mail E-Mail Specifies the vendor’s email address. from the table field
Fax No. Fax No. Specifies the vendor’s fax number. from the table field
Contact Contact Specifies the name of the person you regularly contact when you do business with this vendor. from the table field

Actions

Group Action ToolTip Runs
Actions Comments View or add comments for the record. Page 124 “Comment Sheet”

Procedures

1 local procedures, no public ones.

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

Evidence 1 sources