> For the complete documentation index, see [llms.txt](https://docs.popl.co/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.popl.co/introduction/integrations/microsoft-dynamics-integration/dynamics-field-mapping/sync-logic.md).

# Sync Logic

#### **Sync Logic For All Objects**

After choosing which fields you want to map, you can adjust the sync behavior. You can choose between overwrite, complete if missing, or append.

**Overwrite field:** If a value already exists for an object in Dynamics, replace that data with the Popl field.

**Complete if missing:** Only use the Popl value if the existing field is empty. Otherwise leave the field value as is in Dynamics.

**Append:** Add Popl values to fields that may already have data, instead of replacing it.

***

#### Mapping Types

**Dynamic Mappings -** Dynamic mappings allow Popl to send **real-time data** from each individual lead or contact into the corresponding Dynamics field. This means the value that syncs will **change based on the information captured** during the lead exchange.Use dynamic mappings when you want Dynamics fields to reflect unique data for every synced record.

**Fixed Mappings** - Fixed mappings allow you to send the **same preset value** to a Dynamics field for every synced record. To set a fixed mapping, click into the Popl field, select **“Fixed Mapping,”** and enter the constant value you want applied to all synced leads, contacts, or accounts. Use fixed mappings when you need a **consistent, unchanging value.**

***

#### How We Create *Accounts* Using Fuzzy Matching 

When creating or updating a record, our system attempts to match incoming data to an existing **Dynamics Account** before creating a new one. This helps prevent duplicate accounts and keeps your CRM clean.

#### 1. (Optional) Website-based search — only if enabled in Popl

If the **“Search for existing accounts by Website”**  in advanced settings is enabled:

* We normalize the website value by removing `https://`, `http://`, and `www.`
* We perform a partial (SQL-style `%LIKE%`) search against the **Account Website** field in Dynamics
* If a matching Account is found, that Account is used
* This step is skipped entirely if the setting is disabled

***

#### 2. Fuzzy match by email domain (Account Name field)

* We extract the domain from the contact’s email address (for example, `@company.com`)
* We run a fuzzy search against the **Account Name** field (not the Website field)
* If a close match is found, the existing Account is selected

***

#### 3. Fuzzy match by company name (if provided)

If the incoming lead data includes a company name:

* We run a fuzzy search against the **Account Name** field using the provided company value
* If a close match is found, that Account is used

***

#### Important Note: Enable Dataverse Search for Fuzzy Matching

Fuzzy matching in Microsoft Dynamics relies on **Dataverse Search**. If Dataverse Search is not enabled, fuzzy matching may not function as expected.

#### How to Enable Dataverse Search

1. Go to the **Power Platform Admin Center**
2. Select your **Dynamics 365 environment**
3. Navigate to **Settings → Product → Features**
4. Enable **Dataverse search**
5. Save your changes

Once Dataverse Search is enabled, Popl can properly perform fuzzy matching when syncing leads into Dynamics 365.

***

#### Need Help?

Contact Popl Support – our team is available to assist at <teams@popl.co>.

\
With 🤍 from Popl.&#x20;