Codeunit 89 "Sales-Post + Email"
Base Application · Microsoft.Sales.Posting
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Posting · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Sales Header |
Events published
OnAfterConfirmPost(SalesHeader: Record "Sales Header")(integration): Raised after the user confirms posting the sales document.OnAfterPostAndSend(var SalesHeader: Record "Sales Header")(integration): Raised after the document has been posted and the email has been sent.OnAfterPostAndBeforeSend(var SalesHeader: Record "Sales Header")(integration): Raised after the document has been posted but before the email is sent.OnBeforePostAndEMail(var SalesHeader: Record "Sales Header"; var HideDialog: Boolean; var IsHandled: Boolean; var HideMailDialog: Boolean)(integration): Raised before posting and emailing the sales document.OnSendDocumentReportOnBeforeSendInvoice(var SalesInvoiceHeader: Record "Sales Invoice Header")(integration): Raised before sending the posted invoice via email.
Procedures
InitializeFrom(NewHideMailDialog: Boolean): Initializes the codeunit with settings that control whether the email dialog is displayed.
Plus 4 local procedures.
Triggers
OnRun
Relations
- runs on 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 27 “Confirm Management” (1 call:
ConfirmPostAndDistribute → GetResponseOrDefault) - Codeunit 80 “Sales-Post” (1 call:
Code → (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: "codeunit", object_name: "Sales-Post + Email"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.