Codeunit 46850 "BC14 Migration Provider"
HybridBC14 · Microsoft.DataMigration.BC14Reimplementation
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · BC29-30 · source at ea08af5e · facts from BC29
Procedures
GetDisplayName(): Text[250]GetDescription(): TextGetAppId(): GuidSetupReplicationTableMappings(): Sets up the replication table mappings for all per-company tables we replicate: Setup/Configuration, Master Data, Transaction, and Historical. Called by the platform from Hybrid Cloud Management.FinishCloudMigrationSetup, after EnableReplication has wired up the ADF pipelines and the SaaS production…SetupMigrationSetupTableMappings(): No-op: BC14 reimplementation has no per-database setup tables to replicate during the platform’s setup phase. The setup-phase pipeline runs before SaaS production companies are created, so per-company setup up tables cannot use this channel – they are registered in SetupReplicationTableMappings ins…GetDemoDataType(): Enum "Company Demo Data Type"GetReplicationTableMappingName(): TextGetMigrationSetupTableMappingName(): TextGetCompaniesTableName(): TextShowConfigureMigrationTablesMappingStep(): Boolean
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 40034 “Custom Migration Provider” (3 calls:
GetCompaniesTableName → GetCompaniesTableName,GetMigrationSetupTableMappingName → GetMigrationSetupTableMappingName,GetReplicationTableMappingName → GetReplicationTableMappingName) - Codeunit 46851 “BC14 Migration Setup” (1 call:
SetupReplicationTableMappings → SetupReplicationTableMappings)
Implements
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 Provider"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.