Page 40022 "Cloud Mig Table Mapping API"
HybridAPI · Microsoft.DataMigration.API
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
HybridAPI · Microsoft.DataMigration.API · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | Migration Table Mapping |
| PageType | API |
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 |
|---|---|---|---|
| GroupName | id | Rec.SystemId |
— |
| tableType | Target Table Type | — | |
| applicationID | App ID | — | |
| extensionName | Extension Name | — | |
| tableId | tableID |
— | |
| tableName | Table Name | — | |
| sourceTableName | Source Table Name | — | |
| dataPerCompany | Data Per Company | — |
Procedures
RestoreDefaults(var ActionContext: WebServiceActionContext)DeleteAllForExtension(var ActionContext: WebServiceActionContext)
Triggers
OnAfterGetRecord
Relations
- source table Table 4009 “Migration Table Mapping”
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:
RestoreDefaults → RestoreDefaultMigrationTableMappings)
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: "page", object_name: "Cloud Mig Table Mapping API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.