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

Page 786 "Vendor Picture"

Base Application · Microsoft.Purchases.Vendor

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 23 "Vendor" (relates to)VendorCodeunit 1907 "Camera" (calls, 2 links)CameraRegister a new vendor (Learn pages)Register a new vendor

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 · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Vendor Picture
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 Image Image Specifies the picture of the vendor, for example, a logo. from the table field

Actions

Group Action ToolTip Runs
Processing Take Activate the camera on the device.
Import Import a picture file.
Export Export the picture to a file.
Delete Delete the record.

Procedures

  • TakeNewPicture()

Plus 1 local procedures.

Triggers

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

Evidence 2 sources