Codeunit 6306 "PBI Aged Acc. Calc"
Base Application · Microsoft.Integration.PowerBI
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Integration.PowerBI · BC23-30 · source at ea08af5e · facts from BC29
Procedures
GetValues(var TempPowerBIChartBuffer: Record "Power BI Chart Buffer" temporary; ChartCodeunitID: Integer; ChartName: Text)
Plus 3 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.
- Codeunit 763 “Aged Acc. Receivable” (3 calls:
FormatPeriod → FormatColumnName,FormatPeriod → InitParameters,SetPeriodAndUpdateChart → UpdateDataPerGroup) - Codeunit 1315 “Chart Management” (1 call:
SetPeriodAndUpdateChart → SetPeriodLength) - Codeunit 40 “LogInManagement” (1 call:
SetPeriodAndUpdateChart → GetDefaultWorkDate) - Codeunit 764 “Aged Acc. Payable” (1 call:
SetPeriodAndUpdateChart → UpdateData)
Called by
- Page 6307 “PBI Aged Acc. Payable” (1 call:
OnOpenPage → GetValues) - Page 6308 “PBI Aged Acc. Receivable” (1 call:
OnOpenPage → GetValues)
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: "PBI Aged Acc. Calc"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.