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

Codeunit 104055 "Upgrade - Error Message"

Base Application · Microsoft.Upgrade

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 9999 "Upgrade Tag" (calls, 4 links)Upgrade TagCodeunit 9998 "Upgrade Tag Definitions" (calls, 2 links)Upgrade Tag Definitions

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

Properties

Property Value
Subtype Upgrade

Procedures

2 local procedures, no public ones.

Triggers

OnUpgradePerCompany

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 9999 “Upgrade Tag” (4 calls: UpdateErrorMessageDescription → HasUpgradeTag, UpdateErrorMessageDescription → SetUpgradeTag, UpdateErrorMessageRegisterDescription → HasUpgradeTag, …)
  • Codeunit 9998 “Upgrade Tag Definitions” (2 calls: UpdateErrorMessageDescription → GetErrorMessageDescriptionUpgradeTag, UpdateErrorMessageRegisterDescription → GetErrorMessageRegisterDescriptionUpgradeTag)

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

Evidence 1 sources