Report 313 "Vendor/Item Purchases"
Base Application · Microsoft.Purchases.Reports
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Purchases.Reports · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Vendor/Item Purchases |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | Basic, Suite |
Procedures
InitializeRequest(NewPrintOnlyOnePerPage: Boolean)
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.
- Codeunit 368 “Format Document” (1 call:
OnPreReport → GetRecordFiltersWithCaptions)
Recent changes
- 2026-08-04 #9549 636017 Move Purchases report action tooltips to report objects (main, BC30, refactor)
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: "report", object_name: "Vendor/Item Purchases"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.