pageAdministration & Setupofficial - Microsoftderived - from the source, no model text

Page 46869 "BC14 Company Migration Status"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Table 46855 "BC14CompanyMigrationInfo" (relates to)BC14CompanyMigrationInfo

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · captioned “Company Migration Status” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Company Migration Status
SourceTable BC14CompanyMigrationInfo
PageType Card

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
SettingsLockedInfo Migration has started for this company. Module and transaction settings can no longer be changed because data that has already been migrated cannot be reverted, and a module whose phase has already run will not be triggered again. label —
General Name Name Specifies the company name.
Stop On First Transformation Error Stop On First Error Specifies whether migration should stop immediately when a transformation error is found for this company. Disable to continue and collect all errors in the log.
Modules to Migrate Migrate GL Module Migrate GL Module Specifies whether to migrate General Ledger data. Locked after migration has started.
Migrate Receivables Module Migrate Receivables Module Specifies whether to migrate Customer data. Locked after migration has started.
Migrate Payables Module Migrate Payables Module Specifies whether to migrate Vendor data. Locked after migration has started.
Migrate Inventory Module Migrate Inventory Module Specifies whether to migrate Item data. Locked after migration has started.
Migrate Historical Records Migrate Historical Records Specifies whether to migrate historical records (Posted Sales Invoice, Old G/L Entry archive) for this company. Disable to skip the Historical phase entirely. Locked after migration has started.
Transaction Migration Skip Posting Journal Batches Skip Posting Journal Batches Specifies whether to skip automatic posting of migration journal batches. Enable this if you want to review and post journals manually. Locked after migration has started.
Status Data Migration Started Data Migration Started Specifies whether data migration has started for this company. Once started, additional replication is blocked.
Data Migration Started At Data Migration Started At Specifies when data migration was started for this company.
Migration State Current Migration Step Specifies the current state of the migration process.
Last Completed Phase Last Completed Phase Specifies the last migration phase that was completed successfully.
Phase Progress PhaseProgressText Specifies the progress of the currently running migration phase (Setup / Master / Transactional). Updated as each migrator inside the phase finishes. Historical Data is tracked independently below because it runs asynchronously.
Posting Status PostingStatusText Specifies whether the journal posting step has completed. Posting runs after the transformation phases and is tracked independently of the phase chain.
Historical Data Status HistoricalStatusText Specifies whether the historical data migration has completed. It runs asynchronously after posting and is tracked independently of the phase chain. When failed, the reason is shown.

Actions

Group Action ToolTip Runs
Navigation Migration Errors View migration errors. Page 46863 “BC14 Migration Error Overview”

Triggers

OnOpenPage, OnAfterGetRecord

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "BC14 Company Migration Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources