Codeunit 33 "Vendor Card Calculations"
Base Application · Microsoft.Purchases.Vendor
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Purchases.Vendor · BC23-30 · source at ea08af5e · facts from BC29
Procedures
GetWorkDateLabel(): Text(internal)GetVendorNoLabel(): Text(internal)GetFiltersLabel(): Text(internal)GetBalanceAsCustomerLabel(): Text(internal)GetLinkedCustomerNoLabel(): Text(internal)
Triggers
OnRun
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.
- Page 26 “Vendor Card” (5 calls:
OnPageBackgroundTaskCompleted → GetBalanceAsCustomerLabel,OnPageBackgroundTaskCompleted → GetLinkedCustomerNoLabel,StartBackgroundCalculations → GetFiltersLabel, …)
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: "Vendor Card Calculations"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.