Codeunit 2614 "Feature Data Update Mgt."

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

Event subscriptions

• OnGetImplementation subscribes to Codeunit “Feature Management Facade” OnGetImplementation
• LogErrorHandler subscribes to Codeunit “Feature Data Error Handler” OnLogError
• OnShowTaskLog subscribes to Codeunit “Feature Management Facade” OnShowTaskLog

Procedures

• LogTask(FeatureDataUpdateStatus: Record "Feature Data Update Status"; Description: Text; StartDateTime: DateTime)
• FeatureKeyMatches(FeatureDataUpdateStatus: Record "Feature Data Update Status"; FeatureToUpdate: Enum "Feature To Update"): Boolean

Plus 2 local procedures.

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.

• Page 674 “Job Queue Log Entries” (1 call: ShowTaskLog → (object))

Called by

• Codeunit 1080 “Feature - Fin. Report Default” (1 call: UpdateData → LogTask)
• Codeunit 5409 “Feature - Report Selection” (1 call: UpdateData → LogTask)
• Codeunit 7049 “Feature - Price Calculation” (1 call: UpdateData → LogTask)
• Page extension 7049 “Price Calc. Update Parameters” (1 call: OnOpenPage → FeatureKeyMatches)

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