Codeunit 5447 "Purch. Cr.Memo PDF Doc.Handler"
Base Application · Microsoft.EServices.EDocument
Across versions
- BC23-27not present
- BC28added
- BC29-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.EServices.EDocument · BC28-30 · source at ea08af5e · facts from BC29
Procedures
GeneratePdfBlobWithDocumentType(DocumentId: Guid; DocumentType: Enum "Attachment Entity Buffer Document Type"; var TempAttachmentEntityBuffer: Record "Attachment Entity Buffer" temporary): Boolean: Generates a PDF blob for Purchase Credit Memo
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:
GeneratePdfBlobWithDocumentType → GetAttachmentFileName) - Codeunit 5467 “PDF Document Management” (1 call:
GeneratePdfBlobWithDocumentType → AddToTempAttachmentEntityBuffer) - Codeunit 5511 “Graph Mgt - Purch. Cr. Memo” (1 call:
GeneratePdfBlobWithDocumentType → GetPurchaseCrMemoHeaderFromId)
Implements
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: "Purch. Cr.Memo PDF Doc.Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.