Page 2507 "Upload And Deploy Extension"

System Application · System.Apps · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Extensible	false
SourceTable	Published Application
PageType	NavigatePage

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
Content	Upload Extension	label	—
	Select .app file	`FilePath`	Specifies the file path of the extension.
	Deploy Extension	label	—
	Deploy to	`DeployToValue`	Specifies which version to deploy to.
	Language	`LanguageName`	Specifies the language of the extension.
	Schema Sync Mode	`SyncModeValue`	Specifies how to update the database schema for the extension. The Add option will warn you if the schemas are incompatible and will not apply the change. Force Sync will overwrite the current schema with the new version without warning. Force Sync can lead to data loss.
	By deploying this extension you acknowledge that your data may be sent outside the compliance boundary of Business Central. Each per-tenant extension is subject to its own third party terms and conditions and privacy policies.	`IsAccepted`	Specifies that you accept the privacy policy and the disclaimer.
	Per-Tenant Extension (PTE) Disclaimer	`DisclaimerLbl`	View the disclaimer.
	BestPractices	`'Read more about the best practices for installing and publishing extensions'`	Read more about the best practices for installing and publishing extensions.

Actions

Group	Action	ToolTip	Runs
Processing	Deploy	Deploy
	Cancel	Cancel

Triggers

OnOpenPage

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 43 “Language” (1 call: OnOpenPage → GetWindowsLanguageName)

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: "Upload And Deploy Extension"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.