Customer experience | Sales, Customer Insights,...

Mapping issues while importing data

(2) Share

Report

Posted on by WG-14101734-0

The Microsfort has changed its interface to import the data into Dynamics 365, Sales Hub, and we are facing challenges with field mapping while trying to import. The system does not tell you where it gets stuck.

It just gives us the error "An error has occurred. {1}{0}"

Did anyone else have a similar issue, and is there any solution to it?

Here is the screenshot of the new import interface.

Thank you

Categories:

Dynamics 365 general

I have the same question (9)

All responses (7)

Answers (0)

Suggested answer

Tom_Gioielli 3,084 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
In your application, can you go to the Imports area to see your log of import attempts? You may be able to get more information there.

Gear Icon in Top right Corner > Advanced Settings > Data Management > Imports

It should look like the below. This might give you more information about the error that you can share.

Other things to check in the meantime:

Make sure you have defined lookup field values and that only a single record in the target table matches this criteria

Check your data types to make sure they match (not trying to map strings into integer fields)

Check field lengths for any problems

If working with an xlsx, try it with a CSV and see if it works

Try importing just a few rows, or try just importing a couple columns to see if you still experience the issue.

2 people found this reply helpful.

Was this reply helpful? Yes No
JL-17101305-0 2 on at

Like (0)

Report
Copy link

Link copied!

Why do none of my saved Import Templates work with the new interface, we have about 50 templates, none have worked since the UI changed in our instance on 10/13/25. Also, the "Required" fields when selecting the field from import, doesn't work and still appears in the remaining fields to map but has no option for the "Required" field, so if the import works, the required fields are blank. Also, even if you do map everything needed, there is no "Save" option, so have to remap every single time.

Was this reply helpful? Yes No
matttparker 27 on at

Like (2)

Report
Copy link

Link copied!

We are seeing the same error code. It doesn't actually allow you to finish and submit the import - any error just sends you back to the mapping step. When you check out the import log, all of our attempts show as "Submitted" but do not show any records, which means there is no way to identify what the failure is from.

We typically use xlsx files, but tried with a csv. We received a different error for this, shown before. We don't specify XML anywhere, so I assume that is just the format used by Dynamics under the hood.

We use the provided templates for data import, and did not have this problem a month ago. It definitely seems to be a bug from the recent update.

2 people found this reply helpful.

Was this reply helpful? Yes No
CU18100806-0 2 on at

Like (0)

Report
Copy link

Link copied!

As I search, this error happens because of lookup field mapping issues, especially the owner field. Map only user > full name. All required fields have data. clean your excel file. import a smal test batch first. Hope that racing limits works with you.

Was this reply helpful? Yes No
enterpreysz 7 on at

Like (0)

Report
Copy link

Link copied!

I get XML parsing error as well. Even with very simple uploads. It used to work fine until this new interface emerged.

Was this reply helpful? Yes No
AG-09030358-0 4 on at

Like (1)

Report
Copy link

Link copied!

I ran into the original issue today. After much frustration, it turned out to be the filename. After the re-import failed, I noticed that the timestamp had a p.m. in it. Once I removed that, smooth sailing. That shouldn't break it, but from what I can tell it does.

Was this reply helpful? Yes No
Suggested answer

Niki Patel 85 on at

Like (0)

Report
Copy link

Link copied!
Yes, we’ve encountered this issue with the new import experience in Microsoft Dynamics 365 Sales.

The error “An error has occurred. {1}{0}” is unfortunately very generic and usually indicates that the UI failed to surface the actual backend validation error.

From experience, this is most commonly caused by data mapping issues, especially:

Lookup fields (e.g., Owner, Customer, Parent)

Option set (choice) value mismatches

Invalid data formats (dates, numbers, emails)

Missing required fields or plugin validations

Recommended approach to identify the issue:

Try importing a small dataset with only basic fields (no lookups)

Gradually add fields back one by one to isolate the problematic field

Check the Import Job (Data Management -> Imports) and download the error file for detailed logs

Additional note:
The new UI currently provides limited error visibility, so some level of manual isolation is required.

Please mark as Verified if this answered your question!

Was this reply helpful? Yes No