Codeunit 5569 "Contoso Payments"
ContosoCoffeeDemoDataset · Microsoft.DemoTool.Helpers
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoTool.Helpers · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Permissions | tabledata “Payment Terms” = rim, tabledata “Payment Method” = rim |
Procedures
SetOverwriteData(Overwrite: Boolean)InsertPaymentTerms(Code: Code[10]; DueDateCalculation: Text[30]; DiscountDateCalculation: Text[30]; DiscountPer: Decimal; Description: Text[100])InsertBankPaymentMethod(Code: Code[10]; Description: Text[100]; BalAccountType: Enum "Payment Balance Account Type"; BalAccountNo: Code[20])
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 5206 “Create Payment Terms” (1 call:
OnRun → InsertPaymentTerms) - Codeunit 5295 “Create Payment Method” (1 call:
OnRun → InsertBankPaymentMethod)
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: "Contoso Payments"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.