tableAL Developmentofficial - Microsoftderived - from the source, no model text

Table 1913 "MigrationQB CustomerTrans"

QBMigration

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 2 connected objects and pages

Page 1913 "MigrationQB CustomerTrans" (pages and codeunits on it)MigrationQB CustomerTransQuickBooks Data Migration Extension (Learn pages)QuickBooks Data Migration Ex…

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

QBMigration · BC29-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 1913 “MigrationQB CustomerTrans” (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[100] Customer Number caption DataClassification CustomerContent
2 DocNumber Text[21] Document Number caption DataClassification CustomerContent
3 CustomerRef Text[40] Internal Quickbooks customer reference number. caption DataClassification CustomerContent
4 TxnDate Date Transaction Date caption DataClassification CustomerContent
5 ShipDate Date Ship Date caption DataClassification CustomerContent
6 DueDate Date Due Date caption DataClassification CustomerContent
7 Amount Decimal — DataClassification CustomerContent
8 TransType Option Transaction Type caption DataClassification CustomerContent
9 TxnId Text[30] Internal Quickbooks transaction reference number caption DataClassification CustomerContent
10 GLDocNo Text[30] General Legder Document Number caption DataClassification CustomerContent

Keys

  • Key1: Id, TransType (clustered)

Pages and codeunits on this 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: "MigrationQB CustomerTrans"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources