Page 9820 "Control Add-ins"

Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Control Add-ins
SourceTable	Add-in
PageType	List
UsageCategory	Lists
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
Group	Add-in Name	`Rec."Add-in Name"`	Specifies the name of the Client Control Add-in that is registered on the Business Central Server.
	Public Key Token	`Rec."Public Key Token"`	Specifies the public key token that is associated with the Add-in.
	Version	`Rec.Version`	Specifies the version of the Client Control Add-in that is registered on a Business Central Server.
	Category	`Rec.Category`	Specifies the category of the add-in. There are four categories: DotNet Control Add-in, DotNet Interoperability, Javascript Control Add-in and Language Resource.
	Description	`Rec.Description`	Specifies the description of the Client Control Add-in.
	Resource.HASVALUE	`Rec.Resource.HasValue`	Specifies if the add-in has a resource. The resource can be used to stream the add-in to the Business Central Server instance.

Actions

Group	Action	ToolTip
Control Add-in Resource	Import	Import a control add-in definition from a file.
	Export	Export a control add-in definition to a file.
	Clear	Clear the resource from the selected control add-in.

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