Table 1916 "MigrationQB Item"
QBMigration
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
QBMigration · BC29-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 1916 “MigrationQB ItemTable” (1 Learn page).
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 CustomerContent |
| 2 | Name | Text[100] | — | DataClassification CustomerContent |
| 3 | Description | Text[250] | — | DataClassification CustomerContent |
| 4 | Type | Text[50] | — | DataClassification CustomerContent |
| 5 | UnitPrice | Decimal | — | DataClassification CustomerContent |
| 6 | PurchaseCost | Decimal | — | DataClassification CustomerContent |
| 7 | QtyOnHand | Decimal | — | DataClassification CustomerContent |
| 8 | Taxable | Boolean | — | DataClassification CustomerContent |
| 9 | OrType | Boolean | — | DataClassification CustomerContent |
Keys
- Key1: Id (clustered)
Pages and codeunits on this table
- Page 1916 “MigrationQB ItemTable” (source table)
- Codeunit 1920 “MigrationQB Item Migrator” (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: "MigrationQB Item"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.