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

Table 1602 "Exchange Object"

Base Application · Microsoft.CRM.Outlook

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25unchanged
  4. BC261 fields removed
  5. BC27unchanged
  6. BC282 fields changed
  7. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Page 1626 "Office OCR Incoming Documents" (pages and codeunits on it)Office OCR Incoming DocumentsPage 2021 "Office Attachments" (pages and codeunits on it)Office Attachments

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 Exchange Object
TableType Temporary
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 Type Option — OptionCaption: Email,Attachment
3 Name Δ BC28 Text[250] Name
4 Body BLOB —
5 Parent ID Text[250] —
6 Content BLOB —
8 ViewLink BLOB —
10 Owner Guid — DataClassification EndUserPseudonymousIdentifiers
11 Selected Δ BC28 Boolean Select
12 Content Type Text[250] —
13 InitiatedAction Option — OptionCaption: InitiateSendToOCR,InitiateSendToIncomingDocuments,InitiateSendToWorkFlow,InitiateSendToAttachments
15 IsInline Boolean —
18 RecId RecordId Record ID caption

Keys

  • Key1: Item ID (clustered)
  • Key2: Name

Procedures

  • SetBody(BodyText: Text)
  • GetBody(): Text
  • SetContent(NewContent: InStream)

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: "Exchange Object"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources