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

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Unanswered

Issue During Data Import

(0) ShareShare
ReportReport
Posted on by

Hi All,

I am trying to import data for a custom entity with Opportunity as a lookup field in the custom entity. The import file has Opportunity Name as one of the fields.

There are multiple opportunities with the same name with one being Open and others in closed state. When the users try to import the custom entity records it fails with error "A duplicate lookup reference was found" which is an expected behavior.

But, users complain that they have been performing this earlier as well with multiple opportunities sharing the same name and never encountered this issue.

I tried to reproduce the same in DEV environment where I had sample data with an Opportunity name which has more than one record in the system i.e. 1 Open and others closed and to my surprise it was imported successfully. Any logical explanation for why CRM is behaving differently and how do I get to behave the Production the same as DEV where even though with multiple opportunity records are present with same name, the records are imported successfully and mapped to the correct lookup reference i.e. Opportunity record.

Please no advises for using GUID and also there are no other field in Opportunity entity that holds a unique value. 

Thanks.

Saqib

I have the same question (0)
  • LuHao Profile Picture
    40,888 on at
    RE: Issue During Data Import

    Hi Saqib,

    Please note the following two points.

    1. When importing data, we will choose whether to allow duplicates.

    pastedimage1596183195724v1.png

    2. The duplicate detection rule will only detect the records that the current user can access, but will not detect the records that the current user cannot access.

    Therefore, if the access range of User A is smaller than that of User B, and a record can be accessed by User B but cannot be accessed by User A, then when User A imports a duplicate record with this record, the duplicate detection rule will not be triggered, and when User B imports a duplicate record with this record, the duplicate detection rule will be triggered.

  • Pankaj_Kumar Profile Picture
    70 on at
    RE: Issue During Data Import

    I would suggest you, add prefix/suffix on opportunity Topic for migration which will make a unique value than you can perform data migration.

    You may also use SQL 4 CDS plugin of XRMTool to update prefix/suffix which is very quick.

    Regards,

    Pankaj Kumar

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
DAnny3211 Profile Picture

DAnny3211 433

#2
Abhilash Warrier Profile Picture

Abhilash Warrier 137 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 67 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans