Page 9119 "Sales Doc. Check Factbox"

Base Application · Microsoft.Sales.Document · captioned “Document Check” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Actions

Trigger event subscribers

• OnAfterGetCurrRecordEvent: Codeunit 9070 “Document Errors Mgt.” OnAfterGetCurrRecordSalesDocCheckFactbox

Procedures

• CheckErrorsInBackground(SalesHeader: Record "Sales Header"): Runs a background task to check for document errors in the sales header.

Plus 3 local procedures.

Triggers

OnPageBackgroundTaskCompleted, OnPageBackgroundTaskError

Relations

• source table Table 36 “Sales Header”

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 9079 “Background Error Handling Mgt.” (4 calls: CalcErrors → FeatureTelemetryLogUsageSales, CheckErrorsInBackground → CollectSalesDocCheckParameters, CheckErrorsInBackground → FeatureTelemetryLogUptakeUsed, …)

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: "page", object_name: "Sales Doc. Check Factbox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.