Table 1798 "Data Migration Parameters"
Base Application · System.Integration
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · System.Integration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Data Migration Parameters |
| DataClassification | CustomerContent |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Key | Integer | — | AutoIncrement |
| 2 | Migration Type | Text[250] | — | |
| 3 | Staging Table Migr. Codeunit | Integer | — | DataClassification SystemMetadata |
| 4 | Staging Table RecId To Process | RecordID | — |
Keys
- Key1: Key (clustered)
Pages and codeunits on this table
- Codeunit 6110 “GL Acc. Data Migration Facade” (codeunit runs on it)
- Codeunit 6111 “Vendor Data Migration Facade” (codeunit runs on it)
- Codeunit 6112 “Customer Data Migration Facade” (codeunit runs on it)
- Codeunit 6113 “Item Data Migration Facade” (codeunit runs on it)
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: "table", object_name: "Data Migration Parameters"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.