BC Observatoryunofficial, made by waldo
tableIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table 5338 "Integration Synch. Job"

Base Application · Microsoft.Integration.SyncEngine

Open in Claude5338.mdSource on GitHub

Across versions

  1. BC23present
  2. BC241 procedures removed
  3. BC25-27unchanged
  4. BC2814 fields changed
  5. BC29-30unchanged

Neighbourhood 9 connected objects and pages

Table 5335 "Integration Table Mapping" (relates to)Integration Table MappingPage 5338 "Integration Synch. Job List" (pages and codeunits on it)Integration Synch. Job ListCodeunit 5340 "CRM Integration Table Synch." (event subscribers)CRM Integration Table Synch.Codeunit 7231 "Integration Master Data Synch." (event subscribers)Integration Master Data Synch.Codeunit 5330 "CRM Integration Management" (calls)CRM Integration ManagementTable 5335 "Integration Table Mapping" (referenced by)Integration Table MappingTable 5339 "Integration Synch. Job Errors" (referenced by)Integration Synch. Job ErrorsManage master data synchronization (Learn pages)Manage master data synchroni…Set up companies to synchronize master data (Learn pages)Set up companies to synchron…

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.SyncEngine · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 5338 “Integration Synch. Job List” (2 Learn pages).

Properties

Property Value
Caption Integration Synch. Job
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 ID Guid —
2 Start Date/Time Δ BC28 DateTime Specifies the data and time that the integration synchronization job started.
3 Finish Date/Time Δ BC28 DateTime Specifies the date and time that the integration synchronization job completed.
4 Message Δ BC28 Text[250] Specifies a message that occurred as a result of the integration synchronization job.
5 Integration Table Mapping Name Δ BC28 Code[20] Specifies the name of the table mapping that was used for the integration synchronization job. TableRelation Table 5335 “Integration Table Mapping” (“Integration Table Mapping”.Name)
6 Inserted Δ BC28 Integer Specifies the number of new records that were created in the destination database table (such as the Dynamics 365 Sales Account entity or Business Central Customer table) by the integration synchronization job.
7 Modified Δ BC28 Integer Specifies the number of records that were modified in the destination database table (such as the Dynamics 365 Sales Account entity or Dynamics 365 Customer table) by the integration synchronization job.
8 Deleted Δ BC28 Integer Specifies entries that were deleted when synchronizing Dynamics 365 Sales data and Dynamics 365 data.
9 Unchanged Δ BC28 Integer Specifies the number of records that were not changed in the destination database table (such as the Dynamics 365 Sales Account entity or Dynamics 365 Customer table) by the integration synchronization job.
10 Skipped Δ BC28 Integer Specifies the number of records that were skipped during the integration synchronization job.
11 Failed Δ BC28 Integer Specifies the number of errors that occurred during the integration synchronization job.
12 Synch. Direction Δ BC28 Option Specifies in which direction data is synchronized. OptionCaption: Bidirectional,ToIntegrationTable,FromIntegrationTable
13 Job Queue Log Entry No. Integer —
14 Type Δ BC28 Option Specifies the type of the integration synchronization job. OptionCaption: Synchronization,Uncoupling,Coupling
15 Uncoupled Δ BC28 Integer Specifies the number of records that were uncoupled during the integration synchronization job.
16 Coupled Δ BC28 Integer Specifies the number of records that were coupled by matching an existing entity during the integration synchronization job.

Keys

  • Key1: ID (clustered)
  • Key2: Start Date/Time, ID
  • Key3: Type
  • Key4: Job Queue Log Entry No.
  • Key5: Integration Table Mapping Name

Events published

Procedures

  • DeleteEntries(DaysOld: Integer)
  • GetErrorForRecordID(RecID: RecordID; var IntegrationSynchJobErrors: Record "Integration Synch. Job Errors"): Boolean
  • AreSomeRecordsFailed(): Boolean
  • HaveJobsBeenIdle(JobQueueLogEntryNo: Integer): Boolean
  • CanBeRemoved(): Boolean

Triggers

OnDelete

Relations

Referenced by

2 fields in 2 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

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: "table", object_name: "Integration Synch. Job"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources