Table 4000 "Hybrid Product Type"
HybridBaseDeployment · Microsoft.DataMigration
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 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 | ID | Text[250] | — | DataClassification SystemMetadata |
| 2 | Display Name | Text[250] | The display name of the source product. via Page 4002 “Hybrid Product Types” | DataClassification SystemMetadata |
| 3 | App ID | Guid | — | DataClassification SystemMetadata |
| 4 | Custom Migration Provider | Enum “Custom Migration Provider” | — | enum Enum 4010 “Custom Migration Provider”; DataClassification SystemMetadata |
Keys
- PK: ID (clustered)
Pages and codeunits on this table
- Page 4002 “Hybrid Product Types” (source table)
- Page 40024 “Cloud Mig Product Type API” (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: "Hybrid Product Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.