BC Observatoryunofficial, made by waldo
reportPurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Report 309 "Vendor - Purchase List"

Base Application · Microsoft.Purchases.Reports

Open in Claude309.mdSource on GitHub

Across versions

  1. BC23-28present
  2. BC29declaration changed
  3. BC30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 368 "Format Document" (calls)Format Document

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.Reports · captioned “Vendor Purchase List” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Vendor Purchase List
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite

Procedures

  • InitializeRequest(NewMinAmtLCY: Decimal; NewHideAddress: Boolean)

Plus 1 local procedures.

Triggers

OnPreReport

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.

Recent changes

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: "report", object_name: "Vendor - Purchase List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources