codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 5297 "Create Acc. Schedule Chart"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Finance

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 6 connected objects and pages

Codeunit 5223 "Create Acc. Schedule Name" (calls, 3 links)Create Acc. Schedule NameCodeunit 5298 "Create Acc. Sched. Chart Line" (calls, 3 links)Create Acc. Sched. Chart LineCodeunit 5142 "Contoso Utilities" (calls)Contoso UtilitiesCodeunit 5239 "Contoso Account Schedule" (calls)Contoso Account ScheduleCodeunit 5401 "Create Column Layout Name" (calls)Create Column Layout NameCodeunit 5415 "Finance Module" (calls)Finance Module

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.

ContosoCoffeeDemoDataset · Microsoft.DemoData.Finance · BC29-30 · source at ea08af5e · facts from BC29

Procedures

  • CashCycle(): Text[30]
  • CashFlow(): Text[30]
  • IncomeAndExpense(): Text[30]

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: "Create Acc. Schedule Chart"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources