Codeunit 46853 "BC14 Company Upgrade Task"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · BC29-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnUpgradeBC14Company(var Success: Boolean) (integration): Self-published event whose only subscriber is HandleOnUpgradeBC14Company below. The publish/subscribe boundary forces the subscriber to run in a fresh event-call frame so any AL error inside the migration is captured (GetLastErrorText) and turned into Success=false instead of bubbling up out of OnRu…
  • subscribers: Codeunit 46853 “BC14 Company Upgrade Task” HandleOnUpgradeBC14Company

Event subscriptions

• HandleOnUpgradeBC14Company subscribes to Codeunit “BC14 Company Upgrade Task” OnUpgradeBC14Company

Procedures

3 local procedures, no public ones.

Triggers

OnRun

Relations

• runs on Table 4001 “Hybrid Replication Summary”

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 46854 “BC14 Migration Error Handler” (5 calls: ExecuteCompanyUpgrade → ClearErrorOccurred, ExecuteCompanyUpgrade → ErrorOccurredInCurrentCompany, HandleOnUpgradeBC14Company → ClearErrorOccurred, …)
• Codeunit 46858 “BC14 Migration Status Mgr.” (3 calls: ExecuteCompanyUpgrade → AfterCompanyMigrationCompleted, ExecuteCompanyUpgrade → MarkCompanyCompleted, ExecuteCompanyUpgrade → MarkCompanyStarted)
• Codeunit 46866 “BC14 Telemetry” (3 calls: ExecuteCompanyUpgrade → GetCategory, LogLastError → GetCategory, RunBC14Migration → GetCategory)
• Codeunit 46860 “BC14 Migration Failure Handler” (1 call: ExecuteCompanyUpgrade → MarkUpgradeFailed)
• Codeunit 46862 “BC14 Migration Orchestrator” (1 call: ExecuteCompanyUpgrade → IsCompanySetupCompleted)
• Codeunit 46875 “BC14 Migration Runner” (1 call: RunBC14Migration → RunMigration)

Called by

• Codeunit 46862 “BC14 Migration Orchestrator” (1 call: InvokeCompanyUpgrade → (object))

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