BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6308 "PBI Job Chart Calc."

Base Application · Microsoft.Integration.PowerBI

Open in Claude6308.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Codeunit 759 "Job Chart Mgt" (calls, 3 links)Job Chart MgtPage 6310 "PBI Job Act. v. Budg. Price" (calls)PBI Job Act. v. Budg. PricePage 6311 "PBI Job Profitability" (calls)PBI Job ProfitabilityPage 6312 "PBI Job Act. v. Budg. Cost" (calls)PBI Job Act. v. Budg. Cost

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

Procedures

  • GetValues(var TempPowerBIChartBuffer: Record "Power BI Chart Buffer" temporary; pJobChartType: Option Profitability,"Actual to Budget Cost","Actual to Budget Price")

Plus 2 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 759 “Job Chart Mgt” (3 calls: CalculateValues → CalculateJobCosts, CalculateValues → CalculateJobPrices, CalculateValues → CalculateJobRevenueAndCost)

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: "PBI Job Chart Calc."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources