After the attempt where I checked the box that allowed for duplicates, the import was Completed without failure.
However...
1. The contact is not in the list.
2. The contact name was not in the list before either, so I don't understand why allowing duplicate records allowed the import to be completed.
3. (more of a side question to the above two points) The one field that I was alerted is not mapping is 'Full Name' - is this automatically calculated using 'First' and 'Last' names?
thank you very much.
Hi ETconsultant,
That's because your security role does not have access to "Customize the System". (It doesn't matter if you don't modify the entity field name, you don't have to pay attention here.)
Please note that the “restart the asynchronous service” from the previous post only applies to on-premises, not to online.
If the template cannot be downloaded due to duplicate column headings, and there are not duplicate column headings on the view, you could export the static worksheet. (Duplicate column headings are in the entity and not on this view.)
Uploading the exported Excel static worksheet will ignore fields that do not appear on the view.
I think the problem in your title should be because you have not used the correct upload template.
I tested it in my environment, the process is as follows:
1) Status Reason is Submitted. This process lasts about 3 minutes.
2) Status Reason is Parsing. This process lasts about 3 minutes.
3) Status Reason is Transforming. This process lasts about 1 minutes.
4) Status Reason is Completed. There are imported records in the contact list.
Therefore, the entire process does take a certain amount of time (I only uploaded 5 records), so if you have a large number of records, please wait patiently after the upload to see the results.
Hope this helps.
Best Regards,
Lu Hao
Many thanks for your continued help.
1) I am using a remote Sandbox cloud environment to access the client's CRM, so I have requested the client to try this from their machine to follow the restart asynchronous service steps (e.g. Start > ...)
Re the template:
Upon trying to download the Template from the 'Import Data' dropdown, I have the common error message 'A duplicate column heading exists' and it won't let me download the template.
I understand the fix for this is Go to Settings > Customizations > Customize the system > from the default solution > Select the Account Entity and the Fields > sort by Display Name - and then change the heading name to something else. But after going to Customizations I only am able to see 'Developer Resources' and even when clicking on that, there is no such 'account entity and fields' section.
To your knowledge, might this be caused by the fact I am logging on the cloud-based Sandbox environment?
2) thanks again
Hi ETconsultant,
1) First, delete the file in the "Submitted" status in the "My Imports" list. (If your local file is still there)
This may be because the asynchronous service has stopped, so the uploaded file cannot be parsed. We need to restart the asynchronous service.
You could refer to this article to know how to restart the asynchronous service. (This is a solution for on-premises and does not apply to online.)
In addition, I recommend you use this template:
Select IMPORT DATA>Download Template for Import, use the template downloaded from here to edit records and upload it.
If none of the above works, you could raised a Microsoft support ticket for professional help.
2) The cell format of the template should not be changed. If it changes, the parsing may fail.
One of the points in my last reply was wrong and I am modifying it here. ("Parsing also fails when there are conflicting records in your file.")
After my test, the same records in the file will be parsed successfully.
Therefore, "allow duplicate data" will allow you to completely ignore duplicate requirement.
However, "allow duplicate data" only causes parsing errors, not just the Submitted state.
So I suggest you try the first point above.
Hope this helps.
Best Regards,
Lu Hao
Thank you very much for your helpful and informative response, Lu.
1) I can already see that previous attempts to import data from the source file resulted in partial failures in the 'My Imports' list. The very last file that I tried, which has no 'Partial Failures' yet, is still stuck on 'Submitted' status, rather than 'Completed'. Do you have some idea why it is not completing the task?
2) I agree with you, that duplicates should not be allowed. However, the only change I made when trying to import data from the same source file that did not result in 'partial failure' was checking the allow duplicates checkbox - I do not understand why this has happened. However, as mentioned above, the import is still in 'Submitted' status so it is likely there are data issues. (do you know whether the xlsx cells should be formatted a specific way - e.g. Text?)
3) thank you for clarifying.
Hi ETconsultant,
1) After importing the file, D365 will parse the data from the file. The file import was successful, and the data in the file may not be parsed successfully.
If the data does not meet the business requirements, the parsing will fail. Not only duplicate data, but also other business needs.
Go to Setting > Data Management > Imports, check the resolution of the imported file.
As shown in the image, the file has been imported successfully, but not all data is successfully parsed.
The data of the first file is all parsed successfully. (Successes = Total Processed, Errors = 0)
The data in the sixth file was not fully parsed successfully. (Successes <Total Processed, Errors >0)
Perhaps the file you imported, the number of successfully parsed data is 0. So there is no new data in the list.
If so, then you have a data format error in the file. You need to check to find this error. It should be that all data has this error.
2) I don't recommend using "allow duplicate records" as this may disrupt business requirements.
The effect of allowing duplicate records is: if you already have the same data before, you are allowed to import this data again.
So if you don't have this record before, you are allowed to import it. Allowing duplicate records does not affect the import of new data.
Parsing also fails when there are conflicting records in your file. For example, two contact records for the same phone number. So allowing duplicate records does not help solve duplicate problems within the file.
3) Full Name = First Name + " " + Last Name. This is automatically stitched.
So the Full Name you enter must meet the requirement of this formula.
(A space in the middle is automatically added, you don't need to add a space at the end of First Name or at the beginning of Last Name. But when you manually enter the Full Name, you need to add a space.)
Perhaps it is because the Full Name format error caused the file data to be parsed completely failed.
Hope this helps.
Best Regards,
Lu Hao
thanks for replying. I am importing via a load template in .xlsx file format. I have refreshed my contact list and still cannot see the new contact I added (I tried only one so far, as a test)
(thanks on point 3 - I will ignore the failure of mapping of 'Full Name')
Hi,
Are you ttrying to update ata using excel export & import? Or importing new records? Can you share some more details on steps you performed. Was it Excel file or some other extension?
Regarding your 3 point, it is expected i.e. full name is calculated as firstname & last name
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156