Interface "Custom Migration Provider"

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

Procedures

• GetDisplayName(): Text[250]
• GetDescription(): Text: Gets a description for the migration type. This value is shown in the wizard.
• GetAppId(): Guid: Gets the ID of the app that defines the implementation.
• SetupReplicationTableMappings(): Sets up the replication table mappings. These mappings are used to move the data during the replication phase. This is the default way to move the data.
• SetupMigrationSetupTableMappings(): Sets up the migration setup table mappings. These mappings are used to replicate the data during the setup to SaaS, so the on-premise data can be used to configure the migration. It is recommended to move a small subset of the tables that do not contain large amounts of data, otherwise the setup wil…
• GetDemoDataType(): Enum "Company Demo Data Type": Returns the demo data type that will be used to create the companies in SaaS. Most common types are: “Production - Setup Data Only” - setup data only - this will populate the setup. “Create New - No Data” - empty company. In this case you need to ensure that the setup data is created. This option is…

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