tableRelationship Managementofficial - Microsoftderived - from the source, no model text

Table 1606 "Office Invoice"

Base Application · Microsoft.CRM.Outlook

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC282 fields changed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Page 1632 "Office Invoice Selection" (pages and codeunits on it)Office Invoice SelectionCodeunit 700 "Page Management" (calls)Page Management

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.

Base Application · Microsoft.CRM.Outlook · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption ‘Office Invoice’, Comment = ‘This table is used to keep track of invoices that have been created from the context of an Office add-in.’
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 Item ID Text[250] —
2 Document No. Δ BC28 Code[20] Specifies the number of the related document.
3 Posted Δ BC28 Boolean Specifies whether the document has been posted.

Keys

  • Key1: Item ID, Document No., Posted (clustered)

Procedures

  • ShowInvoice()
  • UnlinkDocument(DocumentNo: Code[20]; IsPosted: Boolean)

Pages and codeunits on this table

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Office Invoice"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources