Codeunit 2103 "O365 Sales Cancel Invoice"
Base Application
Across versions
- BC23present
- BC242 procedures removed
- BC25-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Job Queue Entry |
Procedures
SendInvoiceCancelationEmail(SalesInvoiceHeader: Record "Sales Invoice Header")GetEmailAddress(var SalesInvoiceHeader: Record "Sales Invoice Header"): Text[250]GetEmailSubject(var SalesInvoiceHeader: Record "Sales Invoice Header"): Text[250]IsInvoiceCanceled(SalesInvoiceHeader: Record "Sales Invoice Header"): Boolean
Plus 5 local procedures.
Triggers
OnRun
Relations
- runs on Table 472 “Job Queue Entry”
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 260 “Document-Mailing” (1 call:
SendInvoiceCancelationEmail → EmailFile) - Codeunit 4100 “Temp Blob” (1 call:
SendInvoiceCancelationEmail → CreateInStream)
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: "O365 Sales Cancel Invoice"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.