Report 216 "Archived Sales Order"
Base Application · Microsoft.Sales.Archive
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Archive · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Archived Sales Order |
Procedures
4 local procedures, no public ones.
Triggers
OnInitReport
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” (5 calls:
FormatDocumentFields → SetPaymentTerms,FormatDocumentFields → SetSalesPerson,FormatDocumentFields → SetShipmentMethod, …) - Codeunit 365 “Format Address” (3 calls:
FormatAddressFields → GetCompanyAddr,FormatAddressFields → SalesHeaderArchBillTo,FormatAddressFields → SalesHeaderArchShipTo) - Codeunit 9520 “Mail Management” (1 call:
IsReportInPreviewMode → IsHandlingGetEmailBody)
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: "Archived Sales Order"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.