Page 1610 "Office Add-in Management"

Base Application · Microsoft.CRM.Outlook · captioned “Outlook Add-in Management” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Outlook Add-in Management
SourceTable	Office Add-in
PageType	List
UsageCategory	Administration
ApplicationArea	Basic, Suite

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
Control2	Application ID	Application ID	Specifies the application that is being added.
	Name	Name	Specifies the name of the record.
	Description	Description	Specifies a description of the record. from the table field
	Version	Version	Specifies the version of the record
	Manifest Codeunit	Manifest Codeunit	Specifies the codeunit where the Office add-in is defined for deployment. from the table field

Actions

Group	Action	ToolTip	Runs
Processing	Upload Add-in	Import an XML manifest file to the add-in. The manifest determines how an add-in is activated in Office applications where it is deployed.
	Download Add-in	Export the add-in’s manifest to an XML file. You can then modify the manifest and upload it again.
	Set up Centralized Deployment	Deploy Business Central Outlook Add-ins for specific users, groups, or the entire organization.	Page 1831 “Outlook Centralized Deployment”
	Reset Default Add-ins	Reset the system add-ins to their default state.

Procedures

2 local procedures, no public ones.

Triggers

OnInit

Relations

source table Table 1610 “Office Add-in”

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 1652 “Add-in Manifest Management” (2 calls: OnInit → CreateDefaultAddins, UploadManifest → UploadDefaultManifest)
Codeunit 419 “File Management” (1 call: UploadManifest → UploadFile)

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