12,161
I am trying to update about 500 records from exporting an Advanced Find of Accounts. After editing my data, I try to re-import the file and it fails citing that it was unable to create a duplicate (because I chose not to create duplicates during the Import dialog.)
So, why won't it update the record? Why is trying to create a new record?
*This post is locked for comments
I've found that POWER Automate (FLOW) is really helpful in these cases, you can create your own set of logic to either import or change existing records based on what fields you want to evaluate.
Old thread, but I am experiencing this very issue this morning. Any fix for this?
Well I think I see what is happening now. It is matching on Account name and I do have multiple Accounts with the same name which are differentiated through other descriptive fields e.g. Supplies, Charge, Pro, etc. This never was a problem in the past as I assume it matched on the GUID and not the literal spelling of the name.
Bad form, Microsoft. Why make something less intelligent?
I was able to successfully import/update by choosing 'Yes' to allow duplicates.
That is correct.
I just tried it again with duplicate detection disabled and got the same results.
That is a bit strange and pretty frustrating. So, for me to clearly understand the issue: You are exporting 500 records out of CRM, then you update the records without changing any hidden values or columns. And then you try to re-import to the same CRM organization as to update those records...correct?
If so, I would perhaps look at, perhaps, any duplicate detection rule that may be interfering with the update.
Hi Axel,
The exact error is "A record was not created or updated because a duplicate of the current record already exists." The error code is 0x80040333.
I thought maybe you were on to something as I did have a column comprised of a lookup field. However, I have since removed the column from the view and re-tried the Import to the same result. I have even removed ALL columns except for the one I am trying to update with zero success.
Joe,
I've run into similar issues when there are lookups or columns in the advanced find view from related entities and CRM will hiccup on importing or updating a record if there is a column for a related entity. An example of this can be if you create a custom entity to keep a list of regions and add the region name column to your account entity view used to export.
What is the exact error message you are getting from the Data Management import source file job log? It can give us an indication of where the issue may be.
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,409
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
