Page 1807 "Data Migration Settings"
Base Application · System.Integration
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · System.Integration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Data Migration Settings |
| SourceTable | Data Migration Setup |
| PageType | Card |
| UsageCategory | Administration |
| ApplicationArea | Basic, Suite |
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 |
|---|---|---|---|
| Select default templates for data migration | Default Customer Template | Default Customer Template | Specifies the template to use by default when migrating data for customers. The template defines the data structure and ensures customers are created accurately. |
| Default Vendor Template | Default Vendor Template | Specifies the template to use by default when migrating data for vendors. The template defines the data structure and ensures vendors are created accurately. | |
| Default Item Template | Default Item Template | Specifies the template to use by default when migrating data for items. The template defines the data structure and ensures items are created accurately. |
Triggers
OnOpenPage
Relations
- source table Table 1806 “Data Migration Setup”
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 1806 “Excel Data Migrator” (2 calls:
OpenSettings → (object),ValidateSettings → (object))
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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 Settings"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.