Table 46946 "BC14 Value Entry"
HybridBC14 · Microsoft.DataMigration.BC14Reimplementation
Across versions
- BC23-28not present
- BC29-30present
HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · captioned “Value Entry Migration Data” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Value Entry Migration Data |
| Extensible | false |
| 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 | Entry No. | Integer | — | |
| 11 | Item Ledger Entry No. | Integer | — | |
| 13 | Item Ledger Entry Quantity | Decimal | — | |
| 43 | Cost Amount (Actual) | Decimal | — |
Keys
- Key1: Entry No. (clustered)
- Key2: Item Ledger Entry No.
Recent changes
- 2026-08-04 #9663 Migrate customer, vendor and item transactions for BC14 cloud migration (main, BC30, feature, added)
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: "BC14 Value Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.