codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 5483 "Graph Mgt - Employee"

Base Application · Microsoft.Integration.Graph

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Page 20017 "APIV1 - Employees" (calls, 3 links)APIV1 - EmployeesCodeunit 5468 "Graph Mgt - Complex Types" (calls, 2 links)Graph Mgt - Complex Types

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

Procedures

  • ProcessComplexTypes(var Employee: Record Employee; PostalAddressJSON: Text)
  • PostalAddressToJSON(Employee: Record Employee): Text

Plus 1 local procedures.

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

  • Page 20017 “APIV1 - Employees” (3 calls: OnInsertRecord → ProcessComplexTypes, OnModifyRecord → ProcessComplexTypes, SetCalculatedFields → PostalAddressToJSON)

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

Evidence 1 sources