Report 107 "Customer - Order Summary"
Base Application · Microsoft.Sales.Reports
Across versions
- BC23-26present
- BC272 procedures added
- BC28declaration changed
- BC29declaration changed
- BC30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Sales.Reports · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Customer - Order Summary |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | Basic, Suite |
Procedures
InitializeRequest(StartingDate: Date; ShowAmountInLCY: Boolean): Initializes the report request options for the Customer Order Summary report.
Plus 3 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.
- Codeunit 368 “Format Document” (1 call:
OnPreReport → GetRecordFiltersWithCaptions)
Recent changes
- 2026-09-22 #10495 MSlenejennum/647454/sales internal new body layouts and obsolete current (main, BC30, feature)
- 2026-07-30 #9583 636017 Move Sales report action tooltips to report objects (main, BC30, refactor)
Countries that replace it
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: "Customer - Order Summary"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.