Codeunit 5366 "CRM Archived Sales Orders Job"
Base Application · Microsoft.Integration.D365Sales
Across versions
- BC23present
- BC241 events added
- BC25-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Integration.D365Sales · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Job Queue Entry |
Events published
OnUpdateCRMSalesorderdetailOnBeforeModify(var CRMSalesorderdetail: Record "CRM Salesorderdetail"; SalesLineArchive: Record "Sales Line Archive")+ BC24 (integration)
Procedures
8 local procedures, no public ones.
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.” (3 calls:
UpdateArchivedOrders → BeginIntegrationSynchJobLoging,UpdateArchivedOrders → EndIntegrationSynchJobWithMsg,UpdateArchivedOrders → UpdateSynchJobCounters) - Codeunit 5330 “CRM Integration Management” (1 call:
CreateCRMSalesorderdetail → IsUnitGroupMappingEnabled) - Codeunit 5344 “CRM Product Name” (1 call:
UpdateOrders → FULL)
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 Archived Sales Orders Job"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.