Page 365 "Post and Send Confirmation"
Base Application · Microsoft.Foundation.Reporting
Across versions
- BC23-30present
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Foundation.Reporting · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Post and Send Confirmation |
| SourceTable | Document Sending Profile |
| PageType | ConfirmationDialog |
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 |
|---|---|---|---|
| Content | Send Document to | Rec.GetRecordAsText() |
Specifies how the document is sent when you choose the Post and Send action. |
| ChoicesForSendingTxt | ChoicesForSendingTxt |
— |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord
Relations
- source table Table 60 “Document Sending Profile”
Called by
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 1016 “Jobs-Send” (1 call:
ConfirmSend → (object)) - Codeunit 1017 “Job Tasks-Send” (1 call:
ConfirmSend → (object)) - Codeunit 5979 “Service-Post and Send” (1 call:
ConfirmPostAndSend → (object)) - Codeunit 79 “Sales-Post and Send” (1 call:
ConfirmPostAndSend → (object))
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: "Post and Send Confirmation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.