Codeunit 46860 "BC14 Migration Failure Handler"

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

Properties

Procedures

• MarkUpgradeFailed(var HybridReplicationSummary: Record "Hybrid Replication Summary") (internal)

Plus 3 local procedures.

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 46858 “BC14 Migration Status Mgr.” (3 calls: MarkUpgradeFailed → IsCompanyFailed, MarkUpgradeFailed → MarkCompanyFailed, OnRun → SetSummaryFailed)
• Codeunit 46862 “BC14 Migration Orchestrator” (2 calls: MarkUpgradeFailed → FindLatestReplicationSummary, OnRun → TryFinalizeOverallUpgrade)
• Codeunit 46866 “BC14 Telemetry” (2 calls: LogUnhandledErrorToErrorPage → GetCategory, MarkUpgradeFailed → GetCategory)
• Codeunit 10 “Type Helper” (1 call: NewLine → CRLFSeparator)
• Codeunit 46875 “BC14 Migration Runner” (1 call: OnRun → FailMigration)

Called by

• Codeunit 46853 “BC14 Company Upgrade Task” (1 call: ExecuteCompanyUpgrade → MarkUpgradeFailed)
• Codeunit 46875 “BC14 Migration Runner” (1 call: ContinueCompanyMigration → MarkUpgradeFailed)

Recent changes

• 2026-07-23 #9200 Cloud Migration bug fixes (BC14 reimplementation, custom mapping, OnPrem dev companies) (main, BC30, fix)

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 Migration Failure Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.