Table 2610 "Feature Data Update Status"

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

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	Feature Key	Text[50]	—	DataClassification SystemMetadata
2	Company Name	Text[30]	—	TableRelation Company; DataClassification OrganizationIdentifiableInformation
3	Data Update Required	Boolean	—	DataClassification SystemMetadata
4	Feature Status	Enum “Feature Status”	Current Company Status caption	enum Enum 2610 “Feature Status”; DataClassification SystemMetadata
5	Start Date/Time	DateTime	Specifies the earliest date and time when the task should be run in the background session. via Page 2612 “Schedule Feature Data Update”	DataClassification SystemMetadata
6	Confirmed	Boolean	—	DataClassification SystemMetadata
7	Task Id	Guid	—	DataClassification SystemMetadata
8	Session Id	Integer	—	DataClassification SystemMetadata
9	Server Instance Id	Integer	—	DataClassification SystemMetadata
10	Background Task	Boolean	Specifies whether the task should be run in the current or in the background session. via Page 2612 “Schedule Feature Data Update”	DataClassification SystemMetadata

Keys

PK: Feature Key, Company Name

Pages and codeunits on this table

Page 2612 “Schedule Feature Data Update” (source table)
Codeunit 2612 “Update Feature Data” (codeunit runs on it)
Codeunit 2613 “Feature Data Error Handler” (codeunit runs on it)

Extended by

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: "Feature Data Update Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.