Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
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?
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
Can you check highlighted options are unchecked under duplicate detection settings ?
Here is the direct link to access setting, just replace orgname to actual one -
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'?
Yes, I would except it to work.
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.
Business Applications communities