codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 1326 "Top Five Customers Chart Mgt."

Base Application · Microsoft.Sales.Customer

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Codeunit 1315 "Chart Management" (calls, 3 links)Chart ManagementCodeunit 1328 "Top Customers By Sales Job" (calls)Top Customers By Sales JobPage 21 "Customer Card" (calls)Customer CardPage 22 "Customer List" (calls)Customer 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.Customer · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
SingleInstance true

Procedures

  • UpdateChart(var BusChartBuf: Record "Business Chart Buffer"): Updates the business chart buffer with the top five customers by sales data for doughnut chart visualization.
  • DrillDown(var BusChartBuf: Record "Business Chart Buffer"): Handles drill-down actions on the top five customers chart by opening the customer card or customer list.

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: "Top Five Customers Chart Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources