Table 8615 "Config. Package Data"

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

Properties

Property	Value
Caption	Config. Package Data
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]	Specifies the code of the package that contains the data that is being created. via Page 8627 “Config. Package Data”	TableRelation Table 8623 “Config. Package” (Config. Package); NotBlank
2	Table ID	Integer	—	TableRelation AllObjWithCaption.“Object ID” where(“Object Type” = const(Table)); NotBlank
3	No.	Integer	—	TableRelation Table 8614 “Config. Package Record” (“Config. Package Record”.“No.” where(“Package Code” = field(“Package Code”), “Table ID” = field(“Table ID”)))
4	Field ID	Integer	—	TableRelation Table 8616 “Config. Package Field” (“Config. Package Field”.“Field ID” where(“Package Code” = field(“Package Code”), “Table ID” = field(“Table ID”)))
5	Value	Text[2048]	Specifies the value that has been entered for the field in the configuration package record. As needed, you can update and modify the information in this field, which you can use for comments. You can also correct the errors that are preventing the record from being part of the configuration. This i… via Page 8627 “Config. Package Data”
6	Invalid	Boolean	—
7	BLOB Value	BLOB	—

Keys

Key1: Package Code, Table ID, No., Field ID (clustered)
Key2: Package Code, Table ID, Field ID

Relations

No.: TableRelation Table 8614 “Config. Package Record”
Field ID: TableRelation Table 8616 “Config. Package Field”
Package Code: TableRelation Table 8623 “Config. Package”

Pages and codeunits on this table

Page 8627 “Config. Package Data” (source table)

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