Struggling to import

Customer Engagement
1

Hello, moving back to Dynamics after 3 years of using ConnectWise. I am trying to import my contact and opportunity data. I am unable to download a template, keeps telling me that a duplicate column heading exists, but I cannot find a duplicate in any field. I also keep getting a “number of fields differs from number of column headings” error which I cannot find. Any help?

1 Like
2

It is possible you have a hidden column or it is trying to import an empty one. You might try to delete 10 empty columns to the right of your last column and check for hidden columns

3

This may be due to currency columns. For example, Balance Due and Balance Due (Base) have the same display name, but Balance Due combines currency conversion.

4

Thank you, I am going to check both of these ideas.

5

Hi @Anyse_Spang - did you get this issue sorted? We’ve seen it with standard imports where there are field names (the display names not the schema names) are the same. Let me know if you’re still having an issue, I’d be happy to spend a half hour with you on a call if it would help.

6

Hi Alex, yes I am definitely still having issues. More “cannot create or update due to a duplicate found” errors. I would love any help. Are you available Tuesday June 10th any time between 10:00 AM and 3:00 PM?

7

Sorry, didn’t see this reply! Book a teams call with me Book time with Alex Brown: 30 minutes meeting

9

Hi Anyse,

Hello! That is a classic set of initial roadblocks when moving data back into Dynamics 365. The errors you’re getting are often caused by issues that are invisible in the spreadsheet.

Here is the combined, short, and practical fix:

Quick Fix for Dynamics 365 Import Errors

  1. “Duplicate Column Heading” Fix: This rarely means duplicate words; it means duplicate internal names caused by bad formatting.

    • Action: Delete all blank columns in your Excel sheet. Also, check for and remove any leading or trailing spaces in your column headers (Row 1).

  2. “Number of Fields Differs” Fix: This happens when the system reads data outside your main table range.

    • Action: Ensure your import range is clean. Go to the row immediately after your last data record, select everything below it, and use Delete Rows (not just clear contents). Also, check that no column is using live formulas; Paste Values to convert all calculated fields to static numbers/text.

I hope these simple cleanup steps get your data moving! This method has been highly successful in previous projects, might it work for you as well.

If you still can’t resolve the issue, we’d be happy to set up a free audit session to quickly pinpoint the problem, help you resolve it, and discuss the overall area of scope for your migration.

Feel free to email me directly at hardik.gupta@allgrowtech.com. Good luck!

10

Hi @Anyse_Spang

Is the issue resolved? Or is it still at the same phase?

11

This has been resolved. Thank you.

1 Like