Page 5333 "CRM Skipped Records"

Base Application · Microsoft.Integration.Dataverse · captioned “Coupled Data Synchronization Errors” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Coupled Data Synchronization Errors
SourceTable	CRM Synch. Conflict Buffer
PageType	List
UsageCategory	Administration
ApplicationArea	Suite

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
Group	Table ID	Table ID	Specifies the ID of the table that holds the record. from the table field
	Table Name	Table Name	Specifies the name of the table that holds the record. from the table field
	Description	Description	Specifies the description of the table that holds the record. from the table field
	Record Exists	Record Exists	Specifies if the coupled record exists in Business Central. from the table field
	Coupled To	Int. Description	Specifies the coupled entity in Dynamics 365 Sales
	Coupled Record Exists	Int. Record Exists	Specifies if a coupled entity exists in Dynamics 365 Sales from the table field
	Error Message	Error Message	Specifies why the record was could not be synchronized. from the table field
	Failed On	Failed On	Specifies when the synchronization failed. from the table field

Actions

Group	Action	ToolTip
Processing	Retry	Restore selected records so they can be synchronized.
	Retry All	Restore all records so they can be synchronized.
	Synchronize	Send or get updated data to or from Dynamics 365 Sales.
	Synchronization Log	View integration synchronization jobs for the skipped record.
	Set Up Coupling	Create or modify the coupling to a Dynamics 365 Sales entity.
	Uncoupling Log	View the status of jobs for uncoupling records, for example, in integrations with Dynamics 365 Sales or Dataverse. The jobs were run either from the job queue, or manually, in Business Central.
	Delete Couplings	Delete couplings between the selected Business Central records and Dynamics 365 Sales entities.
	Find for Deleted	Find couplings that were broken when one or more entities were deleted in Business Central. This might take several minutes.
	Restore Records	Restore the deleted coupled entity in Dynamics 365 Sales. A synchronization job is run to achieve this.
	Delete Records	Delete the coupled entity in Dynamics 365 Sales.
	Load More Errors	Reload the error list.

Procedures

SetInitialTableDataFilter(InputInitialTableDataFilter: Text) + BC24 (internal)
SetRecords(var CRMIntegrationRecord: Record "CRM Integration Record"; var CRMOptionMapping: Record "CRM Option Mapping")
SetRecords(var CRMIntegrationRecord: Record "CRM Integration Record")

Plus 6 local procedures.

Triggers

OnAfterGetCurrRecord, OnOpenPage

Relations

source table Table 5374 “CRM Synch. Conflict Buffer”

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 5330 “CRM Integration Management” (2 calls: LoadData → IsCDSIntegrationEnabled, LoadData → IsCRMIntegrationEnabled)

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: "page", object_name: "CRM Skipped Records"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.