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

Codeunit 1640 "Add-in Deployment Helper"

Base Application · System.Integration

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Codeunit 1652 "Add-in Manifest Management" (calls, 3 links)Add-in Manifest ManagementCodeunit 1330 "Instruction Mgt." (calls, 2 links)Instruction Mgt.Codeunit 1630 "Office Management" (calls)Office ManagementPage 1607 "Office Update Available Dlg" (calls)Office Update Available Dlg

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

Procedures

  • CheckVersion(HostType: Text; UserVersion: Text): Boolean

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: "Add-in Deployment Helper"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources