Finance | Project Operations, Human Resources, ...

How to get cause of Data management import errors

(0) Share

Report

Posted on by steen.rabol

136

What seems to be a very simple and straightforward test turns out to be a nightmare - I'm trying to import a Sales Order, using the 'Sales order Composite V3' entity

Environment: Developer dev box, latest D365 Installed product version : 10.0.11 (10.0.464.20007) Installed platform version : Update35 (7.0.5644.41455)

First I created a export project, then exported 1 Sales Order, Source Data format XML-ELEMENT

I modified the <SALESORDERNUMBER> to be empty

Created a Import project for the 'Sales order Composite v3' entity and tried to import the xml file

It fail to import...

There is no information on why.

There is a inflog saying to look at the event viewer of the machine - did that, guess what: "Package "{E36A88C9-1F6D-4282-9ACE-1C41395137E9}" failed. or this: "

Error In SSIS Execution"

One would expect that the XML that is generated by D365 would be easy to import

So... how does one figure out what the issue is ?

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Steen,

There should be an log that lists you the errors that occurred during the import.

If this does not help, try the following:

Export the entity with some records filtered.

Open the exported Excel and compare it with your template.

Probably enter some new data in the exported Excel document and upload it to get the new records imported.

Best regards,

Ludwig

Was this reply helpful? Yes No
WillWU 22,363 on at

Like (0)

Report
Copy link

Link copied!

Hi Steen,

Could you please provide a sample xml file you are using?

Please follow the blog:

hirwani3.rssing.com/browser.php

Make sure that the format of your XML is correct.

Hope this helps.

Was this reply helpful? Yes No
steen.rabol 136 on at

Like (0)

Report
Copy link

Link copied!

I did just as you describe - export 1 record.

Ther error is simply: "Input string was not in a correct format."

Nothing about which field or anything.

The XML was created by D365

Was this reply helpful? Yes No
steen.rabol 136 on at

Like (0)

Report
Copy link

Link copied!

Same result: "Input string was not in a correct format."

Was this reply helpful? Yes No
Suggested answer

Anup Shah MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Try the following

(a) get the Job id (also referred to execution id by support) from the failing project

If it has already been 15-20 minutes since the project failed

- Then In LCS Go to environment monitoring

- Click on "Activity" tab

- Adjust the from date to be a couple of minutes before the time shown in job id and to date to be a minute after.

- In the search box paste the Jobid and search

- If you get a hit, then from the hit copy the activityid

- Paste this in the search box and search again.

Now you have the entire log of what happened from beginning to end. Wherever it fails it will have a call satck and that may give more details to the fieldname it is failing on

(b) Debug the x++ class that is run in processing the composite entity. You can run in batch to get the batch classname

(c) You are not filling in the sales order number is it because you have a number sequence that will generate it? If so then in the composite fields mapping have you set the sales order field to auto generate?

Was this reply helpful? Yes No