Codeunit 9900 "Data Upgrade Mgt."
Base Application · System.Environment.Configuration
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29
Events published
OnIsUpgradeInProgress(var UpgradeIsInProgress: Boolean)(integration)- subscribers: Codeunit 9901 “Data Upgrade In Progress” OnIsUpgradeInProgressHandler
Procedures
SetTableSyncSetup(TableId: Integer; UpgradeTableId: Integer; TableUpgradeMode: Option Check,Copy,Move,Force)SetUpgradeInProgress()IsUpgradeInProgress(): Boolean
Triggers
OnRun
Called by
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 5330 “CRM Integration Management” (1 call:
ReactivateJobForTable → IsUpgradeInProgress) - Codeunit 702 “Sync.Dep.Fld-Utilities” (1 call:
IsFieldSynchronizationDisabled → IsUpgradeInProgress) - Codeunit 7233 “Master Data Management” (1 call:
ReactivateJobForTable → IsUpgradeInProgress)
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: "Data Upgrade Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.