Table 1610 "Office Add-in"

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

Learn documents this table through its pages: Page 1831 “Outlook Centralized Deployment” (1 Learn page).

Properties

Property	Value
Caption	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
1	Application ID Δ BC28	Guid	Specifies the application that is being added.
2	Name Δ BC28	Text[50]	Specifies the name of the add-in.
3	Description Δ BC28	Text[250]	Specifies a description of the record.
5	Version Δ BC28	Text[20]	Specifies the version of the record.
6	Manifest Codeunit Δ BC28	Integer	Specifies the codeunit where the Office add-in is defined for deployment.
10	Deployment Date	Date	—
12	Default Manifest	BLOB	—
13	Manifest	BLOB	—
14	Breaking	Boolean	—
15	Deploy Δ BC28	Boolean	Specifies whether the add-in will be deployed.

Keys

Key1: Application ID (clustered)

Procedures

GetAddins(): Boolean
GetDefaultManifestText(): Text
SetDefaultManifestText(ManifestText: Text)
IsBreakingChange(UserVersion: Text): Boolean

Pages and codeunits on this table

Page 1607 “Office Update Available Dlg” (source table)
Page 1610 “Office Add-in Management” (source table)
Page 1831 “Outlook Centralized Deployment” (source 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.

Codeunit 1630 “Office Management” (1 call: IsBreakingChange → GetOfficeAddinTelemetryCategory)
Codeunit 1652 “Add-in Manifest Management” (1 call: GetAddins → CreateDefaultAddins)

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

Across versions

Neighbourhood 6 connected objects and pages