Page 8614 "Config. Package Card"
Base Application · System.IO
Across versions
- BC23-30present
Neighbourhood 8 connected objects and pages
Base Application · System.IO · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Config. Package Card |
| SourceTable | Config. Package |
| PageType | Document |
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 |
|---|---|---|---|
| General | Code | Code | Specifies a code for the configuration package. |
| Package Name | Package Name | Specifies the name of the package. | |
| 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. | |
| 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. | |
| 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. | |
| Errors | No. of Errors | No. of Errors | Specifies the count of package errors. One line reflects one field of a record that failed validation. |
| Content | Control10 | part Page 8625 “Config. Package Subform” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| 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. | ||
| Export to Excel | Export the data in the package to Excel. | ||
| Import from Excel | Begin the migration of legacy data. | ||
| Show Errors | Open the list of package errors. | ||
| 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 for translation. | ||
| Process Data | Process data in the configuration package before you apply it to the database. For example, convert dates and decimals to the format required by the regional settings on a user’s computer and remove leading/trailing spaces or special characters. |
Procedures
2 local procedures, no public ones.
Triggers
OnOpenPage, OnAfterGetRecord
Relations
- source table Table 8623 “Config. Package”
Pages and codeunits on this table
- Page 8615 “Config. Packages” (card 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 8623 “Dimensions Notifications” (1 call:
OnOpenPage → SendConfigPackageNotificationIfEligible) - Codeunit 8703 “Feature Telemetry” (1 call:
OnOpenPage → LogUptake) - Report 8621 “Config. Package - Process” (1 call:
ProcessPackageTablesWithDefaultProcessingReport → (object))
Called by
- Codeunit 1806 “Excel Data Migrator” (1 call:
OpenAdvancedApply → (object))
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. Package Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.