BC Observatoryunofficial, made by waldo
codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 760 "Trailing Sales Orders Mgt."

Base Application · Microsoft.Sales.Analysis

Open in Claude760.mdSource on GitHub

Across versions

  1. BC23present
  2. BC241 events changed
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Page 760 "Trailing Sales Orders Chart" (calls)Trailing Sales Orders ChartPage 9305 "Sales Order List" (calls)Sales Order List

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.Sales.Analysis · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnBeforeGetSalesOrderAmount(Status: Option; FromDate: Date; ToDate: Date; var Result: Decimal; var IsHandled: Boolean; TrailingSalesOrdersSetup: Record "Trailing Sales Orders Setup") (integration): Raised before calculating the sales order amount for a given status and date range.
  • OnGetSalesOrderCountOnAfterSetFilters(var SalesHeader: Record "Sales Header") (integration): Raised after setting filters on the sales header for counting orders.
  • OnDrillDownOnBeforeRunPage(var SalesHeader: Record "Sales Header"; var IsHandled: Boolean) Δ BC24 (integration): Raised before opening the sales order list page during drill-down.

Procedures

  • OnOpenPage(var TrailingSalesOrdersSetup: Record "Trailing Sales Orders Setup"): Initializes the trailing sales orders setup for the current user when the page opens.
  • DrillDown(var BusChartBuf: Record "Business Chart Buffer"): Opens the sales order list filtered by the selected chart data point.
  • UpdateData(var BusChartBuf: Record "Business Chart Buffer"): Updates the chart data with trailing sales order counts or amounts by status.
  • CreateMap(var Map: array[4] of Integer): Creates a mapping array of sales order status values for chart display.

Plus 4 local procedures.

Triggers

OnRun

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.

Called by

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: "codeunit", object_name: "Trailing Sales Orders Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources