Table 8616 "Config. Package Field"

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

Properties

Property	Value
Caption	Config. Package Field
DataClassification	CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Package Code	Code[20]	—	TableRelation Table 8623 “Config. Package” (Config. Package); NotBlank
2	Table ID	Integer	Specifies the ID for the table that is part of the migration process. via Page 8624 “Config. Package Fields”	TableRelation AllObjWithCaption.“Object ID” where(“Object Type” = const(Table)); NotBlank
3	Field ID	Integer	Specifies the ID of the field for the table that is part of the migration process. via Page 8624 “Config. Package Fields”	TableRelation Field.“No.” where(TableNo = field(“Table ID”)); NotBlank
4	Field Name	Text[30]	Specifies the name of the field for the table that is part of the migration process. The name comes from the Name property for the field. via Page 8624 “Config. Package Fields”
5	Field Caption	Text[250]	Specifies the caption of the field for the table that is part of the migration process. The caption comes from the Caption property for the field. via Page 8624 “Config. Package Fields”
6	Validate Field	Boolean	Specifies whether the information in a field is to be validated during migration. Select the check box if you want to enable validation for the field. This is useful when you want to limit data to a prescribed set of options. via Page 8624 “Config. Package Fields”
7	Include Field	Boolean	Specifies whether the field is included in the migration. Select the check box to include the field in the migration process. By default, when you select the check box, the Field Caption check box is also selected. You can clear this check box if you do not want to enable validation for the field. via Page 8624 “Config. Package Fields”
8	Localize Field	Boolean	Specifies whether the field is to be localized. via Page 8624 “Config. Package Fields”
9	Relation Table ID	Integer	Specifies the ID for the table that contains a field that is related to the one in the migration table. For example, the Post Code table has a relationship with the City field in the Company Information migration table. via Page 8624 “Config. Package Fields”	TableRelation AllObjWithCaption.“Object ID” where(“Object Type” = const(Table)); not editable
10	Relation Table Caption Δ BC24	Text[250]	Specifies the name of the table with a relationship to the migration field. via Page 8624 “Config. Package Fields”	FlowField: lookup(AllObjWithCaption.“Object Name” where(“Object Type” = const(Table), “Object ID” = field(“Relation Table ID”))); not editable
11	Dimension	Boolean	Specifies whether the field in the table is part of the dimension definition set. via Page 8624 “Config. Package Fields”	not editable
12	Primary Key	Boolean	Specifies whether the field is part of the definition of the primary key for the table. via Page 8624 “Config. Package Fields”	not editable
13	Processing Order	Integer	Specifies the order in which the data from the fields in the package should be applied. If your business logic requires that a certain field be filled in before another field can contain data, you can use the Processing Order field to specify the appropriate order. To specify the order, use the Move… via Page 8624 “Config. Package Fields”
14	Create Missing Codes	Boolean	Specifies whether you can create additional values in the database during the configuration migration process. Select the check box to indicate that additional codes can be added to that field in Business Central during the import of data from Excel. via Page 8624 “Config. Package Fields”
15	Mapping Exists	Boolean	Specifies whether the field has a mapping assigned to it that is to be used during data migration. via Page 8624 “Config. Package Fields”	FlowField: exist(“Config. Field Map” where(“Package Code” = field(“Package Code”), “Table ID” = field(“Table ID”), “Field ID” = field(“Field ID”))); not editable
16	AutoIncrement	Boolean	Specifies whether the field has the AutoIncrement property set to Yes, but is not part of the definition of the primary key for the table. via Page 8624 “Config. Package Fields”	DataClassification SystemMetadata
20	XML Field Name	Text[30]	—	DataClassification SystemMetadata

Keys

Key1: Package Code, Table ID, Field ID (clustered)
Key2: Package Code, Table ID, Include Field
Key3: Package Code, Table ID, Validate Field
Key4: Package Code, Table ID, Processing Order

Events published

OnIncludeFieldOnValidateOnAfterCalcShouldRunCheck(var ConfigPackageField: Record "Config. Package Field"; var ShouldRunCheck: Boolean) (integration)
OnBeforeValidateIncludeField(var ConfigPackageField: Record "Config. Package Field"; var IsHandled: Boolean) (integration)
OnBeforeValidateValidateField(var ConfigPackageField: Record "Config. Package Field"; var IsHandled: Boolean) (integration)
OnBeforeValidateFieldIDTableRelation(var ConfigPackageField: Record "Config. Package Field"; var ShouldValidate: Boolean) (integration)
OnValidateFieldOnValidateOnAfterCalcShouldRunCheck(var ConfigPackageField: Record "Config. Package Field"; var ShouldRunCheck: Boolean) (integration)
OnUpdateFieldErrorsOnAfterCalcShouldRunCheck(var ConfigPackageField: Record "Config. Package Field"; var ShouldRunCheck: Boolean) (integration)

Procedures

GetRelationTablesID(): Text
GetElementName(): Text[250]
GetValidatedElementName(): Text

Plus 6 local procedures.

Triggers

OnDelete

Relations

Package Code: TableRelation Table 8623 “Config. Package”
Mapping Exists: CalcFormula Table 8629 “Config. Field Map”

Referenced by

4 fields in 2 objects relate to this table (TableRelation or CalcFormula).

Table 8613 “Config. Package Table”: No. of Fields Available, No. of Fields Included, No. of Fields to Validate
Table 8615 “Config. Package Data”: Field ID

Pages and codeunits on this table

Page 8624 “Config. Package Fields” (source table)

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” (3 calls: UpdateFieldErrors → CleanFieldError, UpdateFieldErrors → FieldError, UpdateFieldErrors → ValidateFieldRelationInRecord)
Codeunit 8615 “Config. Progress Bar” (3 calls: UpdateFieldErrors → Close, UpdateFieldErrors → Init, UpdateFieldErrors → Update)
Codeunit 8614 “Config. XML Exchange” (2 calls: GetElementName → GetElementName, GetUniqueElementName → GetElementName)
Codeunit 8617 “Config. Validate Management” (2 calls: GetValidatedElementName → CheckName, UpdateFieldErrors → EvaluateValue)
Codeunit 10 “Type Helper” (1 call: ThrowErrorIfFieldRemoved → TestFieldIsNotObsolete)

Recent changes

2026-10-06 #12309 Fix infinite recursion in Config. Package Field XML name generation (main, BC30, fix)

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