Page 1799 "Data Migration Overview"

Base Application · System.Integration · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Data Migration Overview
SourceTable	Data Migration Status
PageType	List
UsageCategory	Administration
ApplicationArea	Basic, Suite

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
Control2	Migration Type	Migration Type	Specifies the type of data migration.
	Table Name	`TableNameToMigrate`	Specifies the Table Name
	Migrated Number	Migrated Number	Specifies the number of records that were migrated.
	Total Number	Total Number	Specifies the total number of records that were migrated.
	Progress Percent	Progress Percent	Specifies the progress of the data migration.
	Status	Status	Specifies the status of the data migration.
	Next Task	`NextTask`	Specifies the next task that is needed to complete the migration.
	Error Count	Error Count	Specifies how many records could not be migrated because of an error.

Actions

Group	Action	ToolTip
Processing	Refresh	Refresh this page.
	Stop All Migrations	Stop all data migrations that are in progress or pending.
Navigation	Show Errors	Show the errors that occurred during migration.

Events published

OnRequestAbort() (integration)
- subscribers: Codeunit 1798 “Data Migration Mgt.” OnRequestAbortSubscriber

Trigger event subscribers

OnOpenPageEvent: Codeunit 4016 “Hybrid GP Management” HandleDataMigrationOverviewOpen, Codeunit 46862 “BC14 Migration Orchestrator” HandleDataMigrationOverviewOpen, Codeunit 47013 “SL Hybrid Management” HandleDataMigrationOverviewOpen

Procedures

GoToItemJournal()
GoToGeneralJournalForCustomers()
GoToGeneralJournalForVendors()

Plus 5 local procedures.

Triggers

OnAfterGetRecord, OnOpenPage

Relations

source table Table 1799 “Data Migration Status”

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 6100 “Data Migration Facade” (4 calls: GoToGeneralJournalForAccounts → OnFindBatchForAccountTransactions, GoToGeneralJournalForCustomers → OnFindBatchForCustomerTransactions, GoToGeneralJournalForVendors → OnFindBatchForVendorTransactions, …)
Codeunit 1798 “Data Migration Mgt.” (3 calls: OnAfterGetRecord → DestTableHasAnyTransactions, OnAfterGetRecord → UpdateMigrationStatus, ShowRefreshNotification → IsMigrationInProgress)
Page 39 “General Journal” (3 calls: GoToGeneralJournalForAccounts → (object), GoToGeneralJournalForCustomers → (object), GoToGeneralJournalForVendors → (object))
Page 1797 “Data Migration Error” (1 call: ShowErrors → (object))
Page 40 “Item Journal” (1 call: GoToItemJournal → (object))

Called by

Codeunit 1798 “Data Migration Mgt.” (1 call: ShowDataMigrationOverviewFromNotification → (object))

Documented on Microsoft Learn

Apply Company Configuration Packages

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "page", object_name: "Data Migration Overview"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.