Report 305 "Vendor - Summary Aging"
Base Application · Microsoft.Purchases.Reports
Across versionsobsolete pending since 28.0
- BC23-25present
- BC262 events added
- BC27unchanged
- BC28declaration changed
- BC29declaration changed
- BC30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Purchases.Reports · captioned “Vendor - Summary Aging (Obsolete)” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Vendor - Summary Aging (Obsolete) |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | Basic, Suite |
| ObsoleteState | Pending |
| ObsoleteTag | 28.0 |
| ObsoleteReason | This report is obsolete and will be removed in a future release. See the documentation for alternative options. |
Events published
OnAfterGetRecordIntegerOnBeforeFillColumns(var Vendor: Record Vendor; var DetailedVendorLedgEntry: Record "Detailed Vendor Ledg. Entry")+ BC26 (integration)OnAfterGetRecordVendorOnBeforeFillColumns(var Vendor: Record Vendor; var DetailedVendorLedgEntry: Record "Detailed Vendor Ledg. Entry")+ BC26 (integration)
Procedures
InitializeRequest(NewPeriodStartDate: Date; NewPeriodLength: Text[10]; NewPrintAmountsInLCY: 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)
Documented on Microsoft Learn
Deprecations
- object: Pending 28.0 (#if not CLEAN28), “This report is obsolete and will be removed in a future release. See the documentation for alternative options.”
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 - Summary Aging"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.