codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 5349 "Auto Create Sales Orders"

Base Application · Microsoft.Integration.D365Sales

Across versions

  1. BC23-30present

Neighbourhood 5 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue EntryCodeunit 5330 "CRM Integration Management" (calls)CRM Integration ManagementCodeunit 5335 "Integration Table Synch." (calls)Integration Table Synch.Codeunit 5343 "CRM Sales Order to Sales Order" (calls)CRM Sales Order to Sales OrderCodeunit 5344 "CRM Product Name" (calls)CRM Product Name

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.

Base Application · Microsoft.Integration.D365Sales · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Job Queue Entry

Events published

  • OnBeforeCreateNAVSalesOrdersFromSubmittedCRMSalesorders(var CRMSalesorder: Record "CRM Salesorder"; var IsHandled: Boolean) (integration)
  • OnCreateNAVSalesOrdersFromSubmittedCRMSalesordersOnAfterCRMSalesorderSetFilters(var CRMSalesorder: Record "CRM Salesorder") (integration)

Procedures

1 local procedures, no public ones.

Triggers

OnRun

Relations

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.

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

Evidence 1 sources