---
id: object/page/5333
type: object
title: Page 5333 "CRM Skipped Records"
summary: Page 5333 "CRM Skipped Records" in Base Application (Microsoft.Integration.Dataverse). 3 public procedures. Present since at least BC23, still in BC30, changed in BC24.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: "24"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 8cf44edebb71cd7efbfd00355d4c5a5235d7afdad76cd1572bc0ea19180fd2a1
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Integration/D365Sales/CRMSkippedRecords.Page.al
    title: src/Layers/W1/BaseApp/Integration/D365Sales/CRMSkippedRecords.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 5333
name: CRM Skipped Records
caption: Coupled Data Synchronization Errors
namespace: Microsoft.Integration.Dataverse
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "24"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 0
  procedures: 9
  events: 0
  subscribers: 0
  controls: 8
  actions: 11
relations:
  out: 1
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
  calls: 1
  called_by: 0
  implements: 0
---

# Page 5333 "CRM Skipped Records"

> Page 5333 "CRM Skipped Records" in Base Application (Microsoft.Integration.Dataverse). 3 public procedures. Present since at least BC23, still in BC30, changed in BC24.

Base Application · Microsoft.Integration.Dataverse · captioned "Coupled Data Synchronization Errors" · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Integration/D365Sales/CRMSkippedRecords.Page.al) · 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](../table/5374.md#fields) | Specifies the ID of the table that holds the record. <small>from the table field</small> |
|  | Table Name | [Table Name](../table/5374.md#fields) | Specifies the name of the table that holds the record. <small>from the table field</small> |
|  | Description | [Description](../table/5374.md#fields) | Specifies the description of the table that holds the record. <small>from the table field</small> |
|  | Record Exists | [Record Exists](../table/5374.md#fields) | Specifies if the coupled record exists in Business Central. <small>from the table field</small> |
|  | Coupled To | [Int. Description](../table/5374.md#fields) | Specifies the coupled entity in Dynamics 365 Sales |
|  | Coupled Record Exists | [Int. Record Exists](../table/5374.md#fields) | Specifies if a coupled entity exists in Dynamics 365 Sales <small>from the table field</small> |
|  | Error Message | [Error Message](../table/5374.md#fields) | Specifies why the record was could not be synchronized. <small>from the table field</small> |
|  | Failed On | [Failed On](../table/5374.md#fields) | Specifies when the synchronization failed. <small>from the table field</small> |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| 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)` (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"](../table/5374.md)

## 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"](../codeunit/5330.md) (2 calls: `LoadData → IsCDSIntegrationEnabled`, `LoadData → IsCRMIntegrationEnabled`)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC24

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

## 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.