Once you've mapped your Uniqode fields to Dynamics 365, you can control exactly how each field behaves when a contact syncs — and how Uniqode avoids creating duplicate company records along the way. This article covers the sync behavior options available on every field mapping, the two mapping types you can choose from, and how Uniqode matches existing company records using fuzzy matching.
Sync behavior for field mappings
After mapping a Uniqode field to a Dynamics field, choose how it should behave if the Dynamics Contact already has a value in that field:
Overwrite: If a value already exists on the Contact in Dynamics, replace it with the incoming Uniqode value.
Complete if missing: Only use the Uniqode value if the Dynamics field is currently empty. If it already has a value, leave it as is.
Append: Add the Uniqode value alongside any existing data in the field instead of replacing it.
Mapping types
Every field mapping can be set up as either a dynamic or a fixed mapping.
Dynamic mappings: Send real, per-contact data from Uniqode into the corresponding Dynamics field. The synced value changes based on what was captured during each card exchange. Use this when you want the Dynamics field to reflect unique data for every synced contact.
Fixed mappings: Send the same constant value to a Dynamics field for every synced contact. To set one up, click into the Uniqode field, select Fixed Mapping, and enter the value you want applied to all synced contacts. Use this when you need a consistent, unchanging value — like a lead source label.
How Uniqode matches existing company records
When a contact syncs, Uniqode also tries to match the contact's company to an existing company record in Dynamics before creating a new one. This prevents duplicate company records and keeps your CRM clean. Uniqode checks for a match in the following order:
Website match (optional) — Only runs if Search for existing accounts by website is turned on in Advanced Settings.
Email domain match — Uniqode extracts the domain from the contact's email address (for example, company.com from jane@company.com) and fuzzy-matches it against the company name field in Dynamics. If a close match is found, that record is used.
Company name match — If the synced contact includes a company name, Uniqode fuzzy-matches it against the company name field in Dynamics. If a close match is found, that record is used.
If none of the above find a match, Uniqode creates a new company record in Dynamics.
Note: Fuzzy matching relies on Dataverse Search. If Dataverse Search isn't enabled in your Dynamics environment, fuzzy matching may not work as expected.
Enable Dataverse Search for fuzzy matching
Go to the Power Platform Admin Center
Select your Dynamics 365 environment
Navigate to Settings → Product → Features
Enable Dataverse search
Save your changes
Once Dataverse Search is enabled, Uniqode can properly perform fuzzy matching when syncing contacts into Dynamics 365.
Tips for best results
Use Overwrite sparingly
Reserve Overwrite for fields you know Uniqode should always own, like Job Title captured at the moment of exchange. For fields your sales team edits directly in Dynamics, Complete if missing is usually safer.
Turn on website matching if your team tracks it
Enabling Search for existing accounts by website adds another signal before Uniqode falls back to fuzzy name matching, which reduces duplicate company records for teams with clean website data.
Confirm Dataverse Search is enabled before relying on fuzzy matching
If matches aren't behaving as expected, check the Power Platform Admin Center first — this is the most common reason fuzzy matching underperforms.