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

Codeunit 4782 "Create Mfg Posting Group"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Manufacturing

Across versions

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

Neighbourhood 7 connected objects and pages

Codeunit 4770 "Create Mfg Item" (calls, 5 links)Create Mfg ItemCodeunit 4768 "Create Mfg Posting Setup" (calls, 2 links)Create Mfg Posting SetupCodeunit 5132 "Contoso Posting Group" (calls, 2 links)Contoso Posting GroupCodeunit 4764 "Create Mfg Location" (calls)Create Mfg LocationCodeunit 4775 "Create Mfg Capacity" (calls)Create Mfg CapacityCodeunit 4783 "Manufacturing Module" (calls)Manufacturing ModuleCodeunit 5310 "Create Mfg Item Template" (calls)Create Mfg Item Template

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

Procedures

  • Manufacturing(): Code[20]
  • Finished(): Code[20]

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 Mfg Posting Group"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources