pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 5336 "CRM Coupling Record"

Base Application · Microsoft.Integration.Dataverse

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Table 5332 "Coupling Record Buffer" (relates to)Coupling Record Buffer

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.Dataverse · captioned “Dataverse Coupling Record” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dataverse Coupling Record
SourceTable Coupling Record Buffer
PageType StandardDialog

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
Business Central Business Central Name NAV Name Specifies the name of the record in Business Central to couple to an existing Dataverse record. from the table field
Control13 Synchronize After Coupling Sync Action Specifies whether to synchronize the data in the record in Business Central and the record in Dataverse. from the table field
Dataverse Dataverse Name CRM Name Specifies the name of the record in Dataverse that is coupled to the record in Business Central. from the table field
Control15 Create New Create New Specifies if a new record in Dataverse is automatically created and coupled to the related record in Business Central. from the table field
Content Fields part Page 5328 “CRM Coupling Fields” —

Procedures

  • GetCRMId(): Guid
  • SetSourceRecordID(RecordID: RecordID; IsOption: Boolean)
  • SetSourceRecordID(RecordID: RecordID)

Plus 1 local procedures.

Triggers

OnAfterGetRecord

Relations

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

Evidence 1 sources