Table 1600 "Office Add-in Context"

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

Properties

Property	Value
Caption	Office Add-in Context
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	Email Δ BC28	Text[80]	Specifies the email address of the Outlook contact.
2	Name Δ BC28	Text[250]	Specifies the display name of the Outlook contact.
3	Document Type Δ BC28	Text[20]	Specifies the type that the involved document belongs to.
4	Document No. Δ BC28	Code[250]	Specifies the number of the involved document.
5	Regular Expression Match	Text[250]	—
6	Duration	Text[20]	—
8	Command	Text[30]	—
12	Item ID	Text[250]	—
13	Version	Text[20]	—
14	Contact No.	Code[20]	—
15	Subject	Text[250]	—
16	Item Type	Option	—	OptionCaption: Message,Appointment
18	Mode	Option	—	OptionCaption: Read,Compose
20	Company	Text[50]	—	DataClassification OrganizationIdentifiableInformation

Keys

Key1: Email (clustered)

Procedures

CommandType(): Integer
IsAppointment(): Boolean

Pages and codeunits on this table

Page 1600 “Outlook Mail Engine” (source table)
Codeunit 1636 “Office Contact Handler” (codeunit runs on it)
Codeunit 1637 “Office Document Handler” (codeunit runs on it)
Codeunit 1638 “Office Jobs Handler” (codeunit runs on it)

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: "Office Add-in Context"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.