Codeunit 5355 "CRM Notes Synch Job"

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

Properties

Event subscriptions

• OnFindingIfJobNeedsToBeRun subscribes to Table “Job Queue Entry” OnFindingIfJobNeedsToBeRun
• CreateCRMAnnotationBufferOnAfterInsertRecordLink subscribes to Table “Record Link” OnAfterInsertEvent

Procedures

• GetOrderNotesUpdateFinalMessage(): Text
• CreateAnnotationsForCreatedNotes(): Integer
• CreateNotesForCreatedAnnotations(CreatedAfterDateTime: DateTime): Integer
• ModifyNotesForModifiedAnnotations(ModifiedAfterDateTime: DateTime): Integer

Plus 9 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: UpdateSalesOrderNotes → BeginIntegrationSynchJob, UpdateSalesOrderNotes → BeginIntegrationSynchJobLoging, UpdateSalesOrderNotes → EndIntegrationSynchJobWithMsg, …)
• Codeunit 447 “Record Link Management” (3 calls: CreateCRMAnnotation → ReadNote, ModifyNote → ReadNote, ModifyNote → WriteNote)
• Codeunit 5330 “CRM Integration Management” (1 call: FindCoupledCRMSalesOrder → IsCRMIntegrationEnabled)
• Codeunit 5343 “CRM Sales Order to Sales Order” (1 call: CreateAndCoupleNote → CreateNote)
• 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 Notes Synch Job"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.