> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/deduped/features/duplicate-prevention/prevent-client-side-duplicate-records.md).
# Prevent Client Side Duplicate Records
### Here are two ways DeDupeD can prevent client-side duplicate records:
1. **Prevent duplicates on field changes:** To see how DedupeD helps you prevent duplicates on field changes, follow the steps given below:
* Navigate to **Sales Hub** --> Contact Entity --> Click on **‘New’** button.
* A new contact record form will appear.
* Enter a name in the **‘First Name’** field.
* If a contact record with the same first name already exists, then you will see a pop-up that will prevent you from creating a duplicate.
* If, for some business reasons, you want to ignore duplicates and continue creating the record, then click on **‘Ignore’**.
2. **Prevent duplicate upon saving the record:** To prevent duplicates upon saving the records, follow the steps given below:
* Enter a detail in CRM and click on **‘Save’.**
* If a record with same details already exists in the CRM, then you will see a pop-up that will prevent you from creating a duplicate.
* If, for some business reasons, you want to ignore duplicate and save the record, then click on **‘Ignore and Save’**.
3. **Prevent duplicates blocked by Enforce Duplicate Prevention:**
Not all duplicate rules behave the same way. Depending on how a rule is configured, it can either warn the user about a possible duplicate (and let them save anyway) or block the record from being saved altogether.
This behavior is controlled by the Enforce Duplicate Prevention setting on each matching rule:
* Disabled (No): The rule flags a possible duplicate, but the user can still choose to save the record.
* Enabled (Yes): The rule treats the match as a hard block — the record cannot be saved until it no longer matches.
**Example Scenario**
Suppose a Contact entity has two duplicate detection rules set up like this:
| Matching Rule | Match Type | Enforce Duplicate Prevention |
| ---------------------- | ----------- | ---------------------------- |
| First Name + Last Name | Fuzzy Match | No |
| Email Address | Exact Match | Yes |
**Example 1: Duplicate caught by the First Name + Last Name rule (Enforce Duplicate Prevention = No)**
Since this rule doesn't enforce prevention, the system flags the record as a possible duplicate but still lets the user proceed. The duplicate pop-up shows an 'Ignore and Save' button, so the user can review the match and save anyway if they're confident it's not a real duplicate.
**Example 2: Duplicate caught by the Email Address rule (Enforce Duplicate Prevention = Yes)**
Because this rule enforces prevention, the system treats the match as restricted. The duplicate pop-up shows only a 'Cancel' button — there's no way to save the record until the conflicting email address is changed.
{% hint style="success" %}
For further queries, reach out to us at
{% endhint %}
