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

Codeunit 5138 "Contoso Module Dependency"

ContosoCoffeeDemoDataset · Microsoft.DemoTool

Across versions

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

Neighbourhood 1 connected objects and pages

Codeunit 5193 "Contoso Demo Tool" (calls, 2 links)Contoso Demo Tool

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
Permissions tabledata “Contoso Module Dependency” = rim

Procedures

  • AddDependency(Name: Enum "Contoso Demo Data Module"; DependsOn: Enum "Contoso Demo Data Module")
  • BuildSortedDependencyList(var SortedModulesList: List of [Enum "Contoso Demo Data Module"]; ModulesList: List of [Enum "Contoso Demo Data Module"])

Plus 1 local procedures.

Called by

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

Evidence 1 sources