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

Page 5363 "Match Based Coupling Criteria"

Base Application · Microsoft.Integration.SyncEngine

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 5336 "Integration Field Mapping" (relates to)Integration Field MappingCodeunit 10 "Type Helper" (calls)Type Helper

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

Properties

Property Value
Caption Select Coupling Criteria
SourceTable Integration Field Mapping
PageType Card

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
Synchronize After Coupling SynchAfterMatchBasedCoupling Specifies whether to synchronize data for the coupled records. On pages, the data will synchronize when you choose OK. In the assisted setup guide, the data will synchronize when you choose Finish.
Resolve Update Conflicts ConflictResolution Specifies the strategy to use for automatically resolving conflicts that might occur when synchronizing the coupled records.
Create New If Unable to Find a Match CreateNewInCaseOfNoMatch Specifies whether to create a new Dataverse entity to couple the Business Central record to, in case no match is found by using the matching fields.
Group Field No. Field No. Specifies the number of the field in Business Central. from the table field
Field Name NAVFieldName Specifies the name of the field in Business Central.
Integration Table Field No. Integration Table Field No. Specifies the number of the field in Dynamics 365 Sales. from the table field
Integration Field Name CRMFieldName Specifies the name of the field in Dynamics 365 Sales.
Match on this Field Use For Match-Based Coupling Specifies whether to match on this field when looking for the entity to couple to. from the table field
Case-sensitive Matching Case-Sensitive Matching Specifies whether the matching on this field should be case-sensitive. from the table field
Match Priority Match Priority Specifies in which priority order will the groups of matching fields be used to find a match. from the table field

Actions

Group Action ToolTip Runs
Processing Reset Criteria Resets the coupling criteria.

Procedures

5 local procedures, no public ones.

Triggers

OnOpenPage, OnQueryClosePage, OnAfterGetRecord

Relations

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.

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

Evidence 1 sources