Page 9118 "Purch. Doc. Check Factbox"
Base Application · Microsoft.Purchases.Document
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Purchases.Document · captioned “Document Check” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Document Check |
| SourceTable | Purchase Header |
| PageType | ListPart |
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).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Issues Total | NumberOfErrors |
Specifies the number of issues that have been found in the document. |
| Content | Refresh | RefreshTxt |
— |
| Issues | Error1 | ErrorText[1] |
— |
| Error2 | ErrorText[2] |
— |
Trigger event subscribers
- OnAfterGetCurrRecordEvent: Codeunit 9070 “Document Errors Mgt.” OnAfterGetCurrRecordPurchDocCheckFactbox
Procedures
CheckErrorsInBackground(PurchaseHeader: Record "Purchase Header")
Plus 3 local procedures.
Triggers
OnPageBackgroundTaskCompleted, OnPageBackgroundTaskError
Relations
- source table Table 38 “Purchase 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 → FeatureTelemetryLogUsagePurchase,CheckErrorsInBackground → CollectPurchaseDocCheckParameters,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: "Purch. Doc. Check Factbox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.