Page 1798 "Data Migration About"
Base Application · System.Integration
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · System.Integration · captioned “About Data Migration” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | About Data Migration |
| PageType | StandardDialog |
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 |
|---|---|---|---|
| Content | We’re migrating data to Dynamics 365. Depending on what was chosen, this can be customers, vendors, items, G/L accounts, or all of these entities, plus a history of transactions for them. | label | — |
| Migration will take a few minutes. We’ll let you know when migration is complete. | label | — | |
| In the meantime you can explore Dynamics 365, but do not add new customers, vendors, items, or G/L accounts. | label | — | |
| To monitor progress, choose OK to go to the Data Migration Overview page. | label | — | |
| LearnMore | LearnMoreLbl |
— |
Called by
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 1798 “Data Migration Mgt.” (1 call:
ShowMoreInfoPage → (object))
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: "Data Migration About"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.