Table 5332 "Coupling Record Buffer"

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

Properties

Property	Value
Caption	Coupling Record Buffer
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	NAV Name Δ BC28	Text[250]	Specifies the name of the record in Business Central to couple to an existing Dataverse record.	DataClassification SystemMetadata
2	CRM Name Δ BC28	Text[250]	Specifies the name of the record in Dataverse that is coupled to the record in Business Central.	DataClassification SystemMetadata
3	NAV Table ID	Integer	—	DataClassification SystemMetadata
4	CRM Table ID	Integer	—	DataClassification SystemMetadata
5	Sync Action Δ BC28	Option	Specifies whether to synchronize the data in the record in Business Central and the record in Dataverse.	OptionCaption: Do Not Synchronize,To Integration Table,From Integration Table; DataClassification SystemMetadata
8	NAV Record ID	RecordID	—
9	CRM ID	Guid	—	DataClassification SystemMetadata
10	Create New Δ BC28	Boolean	Specifies if a new record in Dataverse is automatically created and coupled to the related record in Business Central.	DataClassification SystemMetadata
11	Saved Sync Action	Option	—	OptionCaption: Do Not Synchronize,To Integration Table,From Integration Table; DataClassification SystemMetadata
12	Saved CRM ID	Guid	—	DataClassification SystemMetadata
13	CRM Table Name	Code[20]	—	not editable; DataClassification SystemMetadata
14	CRM Option Id	Integer	—	DataClassification SystemMetadata
15	Saved CRM Option Id	Integer	—	DataClassification SystemMetadata
16	Is Option	Boolean	—	DataClassification SystemMetadata

Keys

Key1: NAV Name (clustered)

Events published

OnFindCRMOptionByName(CRMTableID: Integer; var EntityName: Text; var FieldName: Text; var Handled: Boolean) (integration)
OnAfterInitialize(var CouplingRecordBuffer: Record "Coupling Record Buffer") + BC29 (integration)

Procedures

Initialize(NAVRecordID: RecordID; IsOption: Boolean)
Initialize(NAVRecordID: RecordID)
LookUpCRMName()
GetInitialSynchronizationDirection(): Integer
GetPerformInitialSynchronization(): Boolean

Plus 9 local procedures.

Pages and codeunits on this table

Page 5336 “CRM Coupling Record” (source 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.

Codeunit 5334 “CRM Setup Defaults” (4 calls: FindCRMRecordByName → GetNameFieldNo, Initialize → GetCRMTableNo, Initialize → GetDefaultDirection, …)
Codeunit 5332 “Lookup CRM Tables” (2 calls: LookUpCRMName → Lookup, LookUpCRMName → LookupOptions)
Codeunit 5340 “CRM Integration Table Synch.” (1 call: CalcCRMName → LoadCRMOption)
Codeunit 7200 “CDS Integration Mgt.” (1 call: FindCRMOptionByName → GetOptionSetMetadata)

Recent changes

2026-08-28 #10578 [Extensibility Request] issue 30429: add events to disambiguate CRM integration table mappings (main, BC30, feature)

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: "Coupling Record Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.