Codeunit 5352 "CRM Order Status Update Job"

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

Properties

Events published

• OnUpdateSalesOrdersOnBeforeFindIntegrationTableMapping(var IntegrationTableMapping: Record "Integration Table Mapping") + BC29 (integration)

Event subscriptions

• OnFindingIfJobNeedsToBeRun subscribes to Table “Job Queue Entry” OnFindingIfJobNeedsToBeRun

Procedures

• GetOrderStatusUpdateFinalMessage(): Text
• CreateStatusPostOnModifiedOrders(): Integer

Plus 8 local procedures.

Triggers

OnRun

Relations

• runs on Table 472 “Job Queue Entry”

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 5335 “Integration Table Synch.” (4 calls: UpdateSalesOrders → BeginIntegrationSynchJob, UpdateSalesOrders → BeginIntegrationSynchJobLoging, UpdateSalesOrders → EndIntegrationSynchJobWithMsg, …)
• Codeunit 5330 “CRM Integration Management” (2 calls: FindCoupledCRMAccount → IsCRMIntegrationEnabled, FindCoupledCRMSalesOrder → IsCRMIntegrationEnabled)
• Codeunit 5344 “CRM Product Name” (1 call: UpdateOrders → FULL)

Recent changes

• 2026-08-28 #10578 [Extensibility Request] issue 30429: add events to disambiguate CRM integration table mappings (main, BC30, feature)

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: "CRM Order Status Update Job"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.