Page 1796 "Data Migration Error Part"
Base Application · System.Integration
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · System.Integration · captioned “Data Migration Errors” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Data Migration Errors |
| SourceTable | Data Migration Error |
| PageType | ListPart |
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 |
|---|---|---|---|
| Group | Error Message | Error Message | Specifies the error message that relates to the data migration. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Skip Selections | Exclude the selected errors from the migration. | |
| Edit Record | Edit the record that caused the error. | ||
| Migrate | Migrate the selected errors. | ||
| Bulk-Fix Errors | Open a list of all entities that contained an error. You can fix some or all of the errors and migrate the updated data. |
Procedures
4 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord, OnOpenPage
Relations
- source table Table 1797 “Data Migration Error”
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 6100 “Data Migration Facade” (2 calls:
OnAfterGetCurrRecord → OnInitDataMigrationError,StartMigration → StartMigration)
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 Error Part"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.