codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 5692 "Create Extended Sales Document"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Analytics

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 11 connected objects and pages

Codeunit 5537 "Create Item" (calls, 31 links)Create ItemCodeunit 5206 "Create Payment Terms" (calls, 14 links)Create Payment TermsCodeunit 5209 "Create Customer" (calls, 10 links)Create CustomerCodeunit 5416 "Create Salesperson/Purchaser" (calls, 6 links)Create Salesperson/PurchaserCodeunit 5124 "Contoso Sales" (calls, 4 links)Contoso SalesCodeunit 5274 "Create Shipping Data" (calls, 4 links)Create Shipping DataCodeunit 5142 "Contoso Utilities" (calls, 2 links)Contoso UtilitiesCodeunit 5295 "Create Payment Method" (calls)Create Payment MethodCodeunit 5418 "Create Sales Document" (calls)Create Sales DocumentCodeunit 5687 "Analytics Module" (calls)Analytics ModuleCodeunit 5698 "Create Posted Analytics Data" (calls)Create Posted Analytics Data

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

ContosoCoffeeDemoDataset · Microsoft.DemoData.Analytics · BC29-30 · source at ea08af5e · facts from BC29

Procedures

  • AnalyticsReference(): Text

Plus 5 local procedures.

Triggers

OnRun

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.

Called by

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: "Create Extended Sales Document"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources