Codeunit 2613 "Feature Data Error Handler"
System Application · System.Environment.Configuration
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
System Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Feature Data Update Status |
Events published
OnLogError(FeatureDataUpdateStatus: Record "Feature Data Update Status")(integration)- subscribers: Codeunit 2614 “Feature Data Update Mgt.” LogErrorHandler
Triggers
OnRun
Relations
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 2610 “Feature Management Impl.” (1 call:
OnRun → HandleUpdateError)
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: "codeunit", object_name: "Feature Data Error Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.