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

Codeunit 5172 "Employee Media"

ContosoCoffeeDemoDataset · Microsoft.DemoData.HumanResources

Across versions

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

Neighbourhood 2 connected objects and pages

Codeunit 5142 "Contoso Utilities" (calls, 7 links)Contoso UtilitiesCodeunit 5164 "Create Employee" (calls, 7 links)Create Employee

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

Properties

Property Value
Access Internal

Procedures

  • GetManagingDirectorPicture(): Codeunit "Temp Blob"
  • GetSalesManagerPicture(): Codeunit "Temp Blob"
  • GetProductionManagerPicture(): Codeunit "Temp Blob"
  • GetDesignerPicture(): Codeunit "Temp Blob"
  • GetSecretaryPicture(): Codeunit "Temp Blob"
  • GetProductionAssistantPicture(): Codeunit "Temp Blob"
  • GetInventoryManagerPicture(): Codeunit "Temp Blob"

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

  • Codeunit 5164 “Create Employee” (7 calls: CreateEmployee → GetDesignerPicture, CreateEmployee → GetInventoryManagerPicture, CreateEmployee → GetManagingDirectorPicture, …)

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

Evidence 1 sources