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

Codeunit 5382 "Company Creation Contoso"

ContosoCoffeeDemoDataset · Microsoft.DemoTool

Across versions

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

Neighbourhood 5 connected objects and pages

Table 5161 "Contoso Demo Data Module" (relates to)Contoso Demo Data ModuleCodeunit 5193 "Contoso Demo Tool" (calls, 4 links)Contoso Demo ToolCodeunit 1751 "Data Classification Eval. Data" (calls)Data Classification Eval. DataCodeunit 2 "Company-Initialize" (calls)Company-InitializeCodeunit 5279 "Generate Contoso Demo Data" (calls)Generate Contoso Demo Data

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

Properties

Property Value
Access Internal
TableNo Contoso Demo Data Module

Procedures

  • CreateContosoDemodataInCompany(var ContosoDemoDataModuleTemp: Record "Contoso Demo Data Module" temporary; NewCompanyName: Text[30]; NewCompanyData: Enum "Company Demo Data Type")

Plus 1 local procedures.

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.

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: "Company Creation Contoso"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources