BC Observatoryunofficial, made by waldo
codeunitInventoryofficial - Microsoftderived - from the source, no model text

Codeunit 6472 "Serv. Copy Item"

Base Application · Microsoft.Inventory.Item

Open in Claude6472.mdSource on GitHub

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-27unchanged
  4. BC281 procedures changed
  5. BC29-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 730 "Copy Item" (calls, 2 links)Copy Item

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.

Base Application · Microsoft.Inventory.Item · BC25-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • OnAfterCopyItem subscribes to Codeunit “Copy Item” OnAfterCopyItem

Procedures

2 local procedures, no public ones.

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.

  • Codeunit 730 “Copy Item” (2 calls: CopyItemResourceSkills → CopyItemRelatedTableFromRecRef, CopyTroubleshootingSetup → CopyItemRelatedTableFromRecRef)

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

Evidence 1 sources