Page 8615 "Config. Packages"

Base Application · System.IO · captioned “Configuration Packages” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Configuration Packages
SourceTable	Config. Package
PageType	List
UsageCategory	Lists
ApplicationArea	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	Code	Code	Specifies a code for the configuration package.
	Package Name	Package Name	Specifies the name of the package.
	Language ID	Language ID	Specifies the ID of the Windows language to use for the configuration package. Choose the field and select a language ID from the list.
	Product Version	Product Version	Specifies the version of the product that you are configuring. You can use this field to help differentiate among various versions of a solution.
	Processing Order	Processing Order	Specifies the order in which the package is to be processed.
	Exclude Config. Tables	Exclude Config. Tables	Specifies whether to exclude configuration tables from the package. Select the check box to exclude these types of tables.
	No. of Tables	No. of Tables	Specifies the number of tables that the package contains.
	No. of Records	No. of Records	Specifies the number of records in the package.
	No. of Errors	No. of Errors	Specifies the number of errors that the package contains.

Actions

Group	Action	ToolTip
Package	Get Tables	Select tables that you want to add to the configuration package.
	Export Package	Create a .rapidstart file that which delivers the package contents in a compressed format. Configuration questionnaires, configuration templates, and the configuration worksheet are added to the package automatically unless you specifically decide to exclude them.
	Import Package	Import a .rapidstart package file.
	Import Predefined Package	Import one of the preloaded files with packages, such as Evaluation or Standard.
	Export to Excel	Export the data in the package to Excel.
	Import from Excel	Begin the migration of legacy data.
Functions	Apply Package	Import the configuration package and apply the package database data at the same time.
	Copy Package	Copy an existing configuration package to create a new package based on the same content.
	Validate Package	Determine if you have introduced errors, such as not including tables that the configuration relies on.
	Export to Translation	Export the data to a file that is suited translation.

Triggers

OnOpenPage

Relations

card page Page 8614 “Config. Package Card”
source table Table 8623 “Config. Package”

Pages and codeunits on this table

Table 8623 “Config. Package” (lookup page)

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 8611 “Config. Package Management” (1 call: OnOpenPage → ShowRapidStartNotification)
Codeunit 8703 “Feature Telemetry” (1 call: OnOpenPage → LogUptake)

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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