Page 1915 "MigrationQB VendorTrans"
QBMigration
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
QBMigration · captioned “Vendor Transactions” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Vendor Transactions |
| SourceTable | MigrationQB VendorTrans |
| PageType | List |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| General | TransType | TransType | — |
| DocNumber | DocNumber | — | |
| GLDocNo | GLDocNo | — | |
| TxnDate | TxnDate | — | |
| Amount | Amount | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Supporting Pages | Posting Accounts | View QuickBooks posting accounts. | Page 1918 “MigrationQB Posting Accounts” |
Relations
- source table Table 1915 “MigrationQB VendorTrans”
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "page", object_name: "MigrationQB VendorTrans"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.