Table 4019 "Intelligent Cloud Not Migrated"
HybridBaseDeployment · Microsoft.DataMigration
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
HybridBaseDeployment · Microsoft.DataMigration · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
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 | Company Name | Text[250] | Specifies the company name for the table. via Page 4019 “Intelligent Cloud Not Migrated” | DataClassification SystemMetadata |
| 2 | Table Name | Text[250] | Specifies the name of the table. via Page 4019 “Intelligent Cloud Not Migrated” | DataClassification SystemMetadata |
| 3 | Table Id | Integer | — | DataClassification SystemMetadata |
Keys
- PK: Company Name, Table Name (clustered)
Pages and codeunits on this table
- Page 4019 “Intelligent Cloud Not Migrated” (source table)
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: "Intelligent Cloud Not Migrated"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.