Interface "Custom Migration Table Mapping"

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

Procedures

• GetReplicationTableMappingName(): Text
• GetMigrationSetupTableMappingName(): Text: Gets table name of the migration setup table mapping that is used to map the tables from source to destination during cloud migration setup phase. Table name must match the name of the table in SQL database exactly and must have an exact structure as expected by the migration framework, see official…
• GetCompaniesTableName(): Text: Returns the table name of the companies table. This table is used to get the list of the companies for the cloud migration. Companies table exists only in the source database. It can have any name, but it must have 2 fields : [Name] [nvarchar] 30, [Display Name] [nvarchar] 250. [Name] must be primar…
• ShowConfigureMigrationTablesMappingStep(): Boolean: Indicates whether to show the “Configure Migration Tables Mapping” step in the cloud migration wizard. Default value should be to return false, unless there is a need to allow users to change the values provided by the interfaces above.

Implemented by

• Codeunit 40034 “Custom Migration Provider”
• Codeunit 46850 “BC14 Migration Provider”
• Enum 4010 “Custom Migration Provider”

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: "interface", object_name: "Custom Migration Table Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.