Codeunit 40034 "Custom Migration Provider"
HybridBaseDeployment · Microsoft.DataMigration
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
HybridBaseDeployment · Microsoft.DataMigration · BC29-30 · source at ea08af5e · facts from BC29
Events published
OnSetupReplicationTableMappings()(integration)OnSetupMigrationSetupTableMappings()(integration)
Event subscriptions
- HandleOnOpenNewUI subscribes to Page “Intelligent Cloud Management” OnOpenNewUI
Procedures
GetReplicationTableMappingName(): TextGetMigrationSetupTableMappingName(): TextGetCompaniesTableName(): TextShowConfigureMigrationTablesMappingStep(): BooleanGetDisplayName(): Text[250]GetDescription(): TextGetAppId(): GuidGetDemoDataType(): Enum "Company Demo Data Type"SetupReplicationTableMappings()SetupMigrationSetupTableMappings()
Plus 1 local procedures.
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 4001 “Hybrid Cloud Management” (1 call:
HandleOnOpenNewUI → IsCustomMigrationEnabled)
Called by
- Codeunit 46850 “BC14 Migration Provider” (3 calls:
GetCompaniesTableName → GetCompaniesTableName,GetMigrationSetupTableMappingName → GetMigrationSetupTableMappingName,GetReplicationTableMappingName → GetReplicationTableMappingName)
Implements
Implemented by
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: "Custom Migration Provider"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.