Codeunit 9091 "Top Five Vendors Chart"
Base Application · Microsoft.Purchases.Vendor
Across versions
- BC23-26not present
- BC27added
- BC28-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Purchases.Vendor · BC27-30 · source at ea08af5e · facts from BC29
Procedures
UpdateChart(var BusChartBuf: Record "Business Chart Buffer"): Update the chart with the top 5 vendors by purchases.DrillDown(var BusChartBuf: Record "Business Chart Buffer"): Drill down to the vendor card or vendor list page based on the selected vendor.
Plus 4 local procedures.
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 9059 “Acc. Payable Performance” (1 call:
CalcTopPurchasesVendors → ScheduleTopVendorListRefreshTask) - Codeunit 9089 “Top Vendors By Purchases Job” (1 call:
CalcTopPurchasesVendors → UpdateVendorTop10List) - Page 26 “Vendor Card” (1 call:
DrillDownVendor → (object)) - Page 27 “Vendor List” (1 call:
DrillDownOtherVendorList → (object))
Called by
- Codeunit 9059 “Acc. Payable Performance” (2 calls:
DataPointClicked → DrillDown,UpdateChart → UpdateChart)
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 Vendors Chart"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.