BC Observatoryunofficial, made by waldo
tableRelationship Managementofficial - Microsoftderived - from the source, no model text

Table 66 "Merge Duplicates Conflict"

Base Application · Microsoft.CRM.Duplicates

Open in Claude66.mdSource on GitHub

Across versions

  1. BC23present
  2. BC245 fields changed, 1 procedures changed
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Page 704 "Merge Duplicate Conflicts" (pages and codeunits on it)Merge Duplicate Conflicts

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

Properties

Property Value
Caption Merge Duplicates Conflict
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 Table ID Δ BC24 Integer —
2 Duplicate Δ BC24 RecordID —
3 Current Δ BC24 RecordID —
4 Field ID Δ BC24 Integer —
5 Table Name Δ BC24 Text[249] —

Keys

  • Key1: Table ID, Duplicate (clustered)

Procedures

  • Merge(): Boolean Δ BC24

Pages and codeunits on this table

Ask your agent

Procedure bodies are not stored here (D10). 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: "Merge Duplicates Conflict"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources