web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

Data import - remove duplicate detection settings from existing environment/entity

(0) ShareShare
ReportReport
Posted on by 40

I want to import records into my account entity that have unique account names but the same contact. I've turned off all sorts of duplicate detection globally and also adjusted settings to remove duplicate detection at the entity level for account and contact. Imports fail and when I review the report (see lock on screenshot below) it seems to indicate that duplicate detection is still on. How do I turn this off?

7080.forum.png

I made a new sandbox environment and removed all the duplicate settings before I ever imported anything, and then I was able to import duplicates. But with my existing entity it seems as if the out of the box controls aren't doing the job. I wonder whether or not a deeper cure requiring C# is required, but that's beyond my present ability. Any tips would be appreciated. Thanks, GERALD DAHL

I have the same question (0)
  • Suggested answer
    Satish Tiwari - CRM Profile Picture
    Microsoft Employee on at

    Hello Gerald,

    Can you check highlighted options are unchecked under duplicate detection settings ?

    pastedimage1594547662371v1.png

    Here is the direct link to access setting, just replace orgname to actual one - 

    orgnam.crm.dynamics.com/.../duplicatedetectionsettings.aspx

  • Gerald Dahl Profile Picture
    40 on at

    Thanks Satish, I've tried this, but, I thought of something new that I might need to try.

    I see that I have two lookups in Accounts that point to Contacts, one is Primary Contact and another is a custom field that I created called relatedContact. (When I created relatedContact I wasn't aware that Primary Contact was also there.)

    I think I will try to delete relatedContact and then use Primary Contact instead whenever I have a need to identify and refer to an individual as a relatedContact.

    Do you think if I delete the relatedContact field and its data and its relationships and if I set the duplicate rules as you have illustrated that I will be able to import duplicate records without getting the warning I am currently getting which says 'A duplicate lookup reference was found'?

    Thanks,

    GERALD DAHL

  • Suggested answer
    Satish Tiwari - CRM Profile Picture
    Microsoft Employee on at

    Yes, I would except it to work.

  • Verified answer
    Gerald Dahl Profile Picture
    40 on at

    FYI I discovered that because I had an inactive contact with the same name that my imports were failing. After I deleted the inactive contact with the same name then I had success with imports. Thank you.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 184 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 125

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans