Hi DP-09071335-0,
You're asking how to expose a custom field—specifically "BC No." (new_bcno)—in the Match-Based Coupling Criteria page (ID 5363) when working with the standard CONTACT integration record in BC 20 On-Premise. You've already mapped the field in Integration Field Mapping (5336), but it doesn’t appear in the coupling grid.
This is a known limitation in older versions of BC, especially on-premise, where the Match-Based Coupling Criteria page only displays fields that are explicitly enabled and linked through the integration metadata.
Here’s how you can work around it:
1. Extend the Integration Field Mapping Table (5336)
You’ll need to create a new record in Integration Field Mapping manually via AL code to link your custom Dataverse field to the BC field.
al
procedure AddCustomFieldMapping()
var
IntegrationFieldMapping: Record "Integration Field Mapping";
begin
IntegrationFieldMapping.Init();
IntegrationFieldMapping."Integration Table Mapping ID" := 'CONTACT'; // Use actual GUID or lookup
IntegrationFieldMapping."Field Name" := 'No.';
IntegrationFieldMapping."Integration Field Name" := 'new_bcno';
IntegrationFieldMapping."Direction" := IntegrationFieldMapping."Direction"::Bidirectional;
IntegrationFieldMapping.Insert(true);
end;
Make sure this runs after your integration setup is initialized.
2. Extend the Match-Based Coupling Criteria Page (5363)
This page uses a filtered view of Integration Field Mapping. You’ll need to ensure your custom field is flagged as eligible for matching.
- Add a new field to the page via a page extension
- Set
Match on this Field and Case-sensitive Matching to true
- Optionally, set
Match Priority to guide the matching logic
3. Validate Field Visibility
After inserting the mapping, restart the client and open the Match-Based Coupling action again. Your custom field should now appear in the grid.
If it still doesn’t show:
- Check if the field is enabled in the
FieldGroup of the Contact table
- Confirm that the integration metadata is refreshed (you may need to restart the service tier)
Here’s an example of how custom fields appear in the Match-Based Coupling grid once properly mapped:
Customize Dataverse Integration – Microsoft Learn
Add Field to FieldGroup – Saurav Dhyani
Dataverse Field Mapping – Dynamics 365 Lab
Coupling and Synchronizing Records – Microsoft Learn
If you find this helpful, feel free to mark this as the suggested or verified answer.
Cheers
Jeffrey
