Codeunit 104046 "Upgrade Monitored Field"
Base Application · Microsoft.Upgrade
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Upgrade · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Subtype | Upgrade |
Procedures
1 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” (2 calls:
UpgradeNotificationCount → HasUpgradeTag,UpgradeNotificationCount → SetUpgradeTag) - Codeunit 6060 “Hybrid Deployment” (1 call:
UpgradeNotificationCount → VerifyCanStartUpgrade) - Codeunit 9998 “Upgrade Tag Definitions” (1 call:
UpgradeNotificationCount → GetUpgradeMonitorNotificationUpgradeTag)
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 Monitored Field"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.