Dynamics 365 - Data Model Framework (1/3)

With every implementation project it’s useful to upload data to the system instead of typing in manually. With the module [Data management] you are able to do this. In this mini [Data management] series I’ll give tips and go into errors you might run into using this module.

Part 1 – Job would not accept file

Part 2 – Job accepts file but provides errors

Part 3 – Import job finished with errors

General import tips

• In order to prepare you Excel sheet, you can export the entity first to check what field are available.
• You can use CONTOSO demo environment to export files. In this way you have sample data.
• Use Excel in TEXT mode to prepare your data. (format the whole sheet as TEXT)
• I prefer to use only 1 sheet per Excel, otherwise the import keeps asking which sheet to import
• Check for empty rows, empty columns and non-printable characters (more in part 2)
• Keep track of drop-down options in your data. If you specify new ones and they are not setup in the system, you will run into errors.
• Use Packages to move data from one environment to the other (all setup is in the package, that saves times for setting up the import project). Advise; only move static and dynamic data in this way, not parameters. As some parameters are not set correctly when importing packages.
• Test your imports several times and fix issues before going live!
• Keep track on dependencies, for example if you miss an item, you could get errors when importing dynamic data, sales orders, purchase orders, inventory etc.

Job would not accept the file

Sometimes the import project would not accept your file and you get strange errors.

 “Query validation failed – External table is not in the expected format.”

• Refresh you entity list
• Rebuild the entity from scratch
• Restart system (cloud hosted)
• Sync database (cloud hosted)

“Sample file is in incorrect format”

• The [Source data format] is different from the file format you are uploading.
• For example; you want to upload a CSV file but selected the Excel as a source.

“There are field(s) which are not mapped to the Entity – xxxxx”

• The file formats are correct, but the source file does not contain enough fields which can be mapped to the entity name.
• For example; you tried to upload a [Released Product] list on a [Customers V3] entity.
• If the key fields are part of your file and you added 1 or 2 extra. The system will accept the file, but you have to specify in the data mapping the type of fields (more of that in part 2).