codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 436 "Acc. Sched. BarChart DrillDown"

Base Application · Microsoft.Finance.FinancialReports

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 450 "Bar Chart Buffer" (relates to)Bar Chart BufferCodeunit 8 "AccSchedManagement" (calls, 5 links)AccSchedManagementPage 570 "Chart of Accounts (G/L)" (calls)Chart of Accounts (G/L)

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

Properties

Property Value
TableNo Bar Chart Buffer

Events published

  • OnAfterAccSchedManagementSetGLAccRowFilters(var GLAcc: Record "G/L Account"; var AccScheduleLine: Record "Acc. Schedule Line"; var ColumnLayout: Record "Column Layout") (integration): Integration event raised after account schedule management sets G/L account row filters. Enables additional filter customization for drill-down from bar chart data points.
  • OnAfterAccSchedManagementSetGLAccColumnFilters(var GLAcc: Record "G/L Account"; var AccScheduleLine: Record "Acc. Schedule Line"; var ColumnLayout: Record "Column Layout") (integration): Integration event raised after account schedule management sets G/L account column filters. Enables additional filter customization for drill-down from bar chart data points.

Triggers

OnRun

Relations

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.

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: "Acc. Sched. BarChart DrillDown"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources