Page extension 46870 "BC14 Cloud Migration Mgmt Ext"

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

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
modify(CompaniesStatusText)	Companies Replication status	modifies `CompaniesStatusText`	—
addlast(OveralInformation)	Companies Upgrade status	`CompanyUpgradeStatusText`	Specifies the upgrade-phase status summary for all companies (separate from the replication-phase Companies Replication status above). Format: Pending: X, Started: Y, Completed: Z, Failed: W. Drill down to see per-company status.
	Upgrade Error Details	`UpgradeErrorDetailsText`	Specifies the accumulated error messages and call stacks captured for failed companies during the Business Central 14 upgrade.

Actions

Group	Action	ToolTip	Runs
modify(RunDataUpgrade)	RunDataUpgrade	—	modifies `RunDataUpgrade`
addlast(Processing)	Configure BC14 Re-implementation	Configure default re-implementation settings (modules, posting, error handling). Per-company overrides, upgrade timing, and re-implementation errors are reachable from inside.
	BC14 Migration Errors	View the BC14 migration errors collected across all companies and migrators.	Page 46863 “BC14 Migration Error Overview”
	Resume Business Central 14 Upgrade	Continue the Business Central 14 upgrade after a failure or interruption. If any company is Pending, the next one is dispatched. If only Failed companies remain, you are prompted to reset them to Pending and retry.

Procedures

6 local procedures, no public ones.

Triggers

OnOpenPage, OnAfterGetCurrRecord

Relations

extends Page 40063 “Cloud Migration Management”

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.” (4 calls: RerunFailedCompanies → FilterFailedCompanies, ResumeBC14UpgradeAction → GetCompanyStatusCounts, UpdateCompanyUpgradeStatus → GetCompanyStatusCounts, …)
Codeunit 46862 “BC14 Migration Orchestrator” (3 calls: ResumeBC14UpgradeAction → DispatchNextReadyCompany, ResumeBC14UpgradeAction → FindLatestReplicationSummary, UpdateUpgradeErrorDetails → FindLatestReplicationSummary)
Codeunit 46861 “BC14 Wizard” (1 call: OnOpenPage → GetBC14MigrationEnabled)
Codeunit 46875 “BC14 Migration Runner” (1 call: RerunFailedCompanies → ContinueMigrationForCompany)

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: "pageextension", object_name: "BC14 Cloud Migration Mgmt Ext"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.