Importing Opportunity Products

(2) Share

Report

Posted on by David_Evans

Hello,

I'm trying to import a single opportunity product into D365 Sales.

I've exported an existing Opportunity Product and copied the values onto the Import Template for Opportunity products as taken from the Templates for data Import from the Data Management section of the Power Platform Environment Settings, but whatever I do i get the error 'The source data is not in the required format'

When expand the error line I get this

Categories:

Dynamics 365 Sales

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Suggested answer

Tom_Gioielli 3,086 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

The error you mention on the import and the screenshot are actually two separate items. The screenshot issue is from the import error tool. There is no separate form to open to review the import errors, you can only view them in the subgrid.

The import error is indicating that something in your import is incorrect and you are receiving an error in the format for a field. Do you have an example of the import row and the fields you are importing into? It could be a mismatched option set, a date and time format that is not allowed, or something like your [Amount] field having a currency symbol in the import file instead of just being a number (10.00 vs $10.00).

Was this reply helpful? Yes No
David_Evans 38 on at

Like (1)

Report
Copy link

Link copied!

Hi Tom,

Thanks for the reply. I've attached the (renamed) file I was trying to import.

It's not easy to problem solve this because the error messages are somewhat brief, so any tips are welcome.

David

TestLoadOf Opport...

Was this reply helpful? Yes No
Verified answer

Daivat Vartak (v-9d... 7,841 Moderator on at

Like (2)

Report
Copy link

Link copied!

Hello David,

I saw that other people have had trouble importing Opportunity Products using Excel, just like you. Please take a look at those discussions. They might have solutions or tips that can help you fix your problem. Your error message is too general, so we need more details to help you properly.

Importing Opportunities with Opportunity Products: https://community.dynamics.com/forums/thread/details/?threadid=48e4d2d5-54d7-4be9-ad5f-934d2797bf65

Opportunity Product - impossible to import; invisible lookup field, although it should be required: https://community.dynamics.com/forums/thread/details/?threadid=80655173-2873-4305-aa8b-6b900e539af2

Try this: Make one Opportunity Product in your system, then export it using Advanced Find. This will give you a perfect example of how the data should look. Compare this exported file to your import template. You can even try importing the exported file back in. This will help you see if your template is the problem.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

Regards,

Daivat Vartak

Was this reply helpful? Yes No
Suggested answer

Tom_Gioielli 3,086 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

So sorry I missed this reply @David_Evans .

From the file you sent, the only thing I can imagine being an issue on import might be the Opportunity. Since that is going to be imported into a Lookup field, by default the import process will want something unique. A GUID can often be used, or if you use name you need to make sure there are no duplicate named opportunities out there.

If you go to your import jobs, open up the one where this error occurred. You should be able to see a subgrid of Errored out rows in your import, and the far-right column will indicate what the issue was. If this was a problem with the Opportunity lookup field, you would see something like "Lookup reference not found" or something similar.

Your original error looked like you were trying to open up the error line in the log, which isn't possible because the error lines don't have a form associated with them. Are you able to see what the issue was if you scroll to the right on the grid

EDIT: Sorry, I just saw you listed the error above. To the left of the error description, it should show you the actual value from the import that caused the error. Can you post what that was?

Was this reply helpful? Yes No