Data Management Importing Tips for D365 for Finance and Operations: Part 2
Posted on: May 24, 2018 | By: Jarrod Kraemer | Microsoft Dynamics AX/365
Authored by: Chris Rusing
In part one of this blog, I discussed the important configuration setup that must be addressed prior to importing data through data management. If you haven’t done so already, please read this blog. Part two of this series will provide examples of errors you may receive while importing data and how to troubleshoot them.
Before we get into the different types of errors you may encounter, I want to quickly demonstrate where to navigate to see these error messages. When an import fails, go to the top left corner and click View execution log.
Once you are there, click on the Staging log details button in the top of the form. If that option is not available, click the View staging data button. These forms will provide you with the error message(s).
Occasionally, error messages will appear in the Log text section too.
The first error I would like to discuss is the backslash character error. Often, your import file will involve a record in the system like a vendor, customer or fixed asset that contains a dash in the number sequence. For example, I’m trying to import lines to acquire the fixed asset record ‘USSSMACH-000003’. If you simply leave the fixed asset record as is, you will receive an error like this:
Results. Fixed assets accounts have only one segment and the specified value USSSMACH-000003 has more than one segment.
Things to try:
• Make sure that the Fixed assets account specified has only one segment.
• Make sure that the Fixed assets account specified that includes the chart of accounts delimiter character in the name escapes the delimiter character with a backslash character ''.
Results. Error found when validating record.
The key is in the second bullet point- you need the backslash character ‘’ to differentiate the delimiter character from the chart of accounts, ‘-‘. Please note that this the default delimited character for chart of accounts. So, I will alter my import file to include that backslash character in the fixed asset account field and import the file again.
The next error is the ‘Invalid Enum Value’ error. This occurs when you accidentally fat finger a standard drop-down value from D365. In the image below, you can see that I have my transaction type as ‘Acquisitions’ when it should be ‘Acquisition’. The Acquisition transaction type is a standard selection from the available drop-down, so the system throws an error that the value is invalid.
Lastly, an error message occurs when you change the name of the tab from the Excel file. When you are initially setting up the import job in data management, you upload the data file to map the source fields to the staging fields. The data project will save the tab name and it will look for that exact name in the Sheet lookup field. For example, when I click Run project on my general journal upload project, you can see that the project is looking up ‘Sheet1’.
However, my current sheet is named ‘Sheet2’ which will throw this error: Exception from HRESULT: 0xC02020E8. You must have the same sheet name as the original file used to create the data project to avoid this error. Changing my tab back to ‘Sheet1’ would alleviate the issue in this situation.
In part three of this blog series, I will discuss tips and tricks to help get through data management imports. For additional information please feel free to reach out to us at firstname.lastname@example.org or (312) 345-8817.
All the best!
25 Brilliant Ideas to Outsmart Your Competition with Microsoft Dynamics
Top 10 Inventory & Operations Decisions Distributors Are Making Blind
2020 Nucleus Research Report on ERP Technology