Dynamics 365 from its predecessor’s inception Axapta, provide integrated and continuously updated foreground of core business processes and application architecture. Since data is the principle driving force for any ERP business process to proceed. Dynamics 365 likewise it’s other family products, provides a robust data management framework to import data which assists information flow between all business functions.

Before we moving on to discussing data Importing techniques; We must conceive that importing/migration could be critical to conducive implementation and thus would require significant planning and also require to ask us few questions.

  • What sort of record do we need to import?
  • What is the source of the data?
    The data could be in variety of sources which push forward us to foresee ways for importing from individual sources.
  • Will we be importing any data fields that are unique to your business?
    For instance, while importing data from Dynamics Ax 2012 or earlier, we could come up to a scenario where a field or a table might not exist in D365. Therefore, for such scenario D365 enables us to upgrade code using extension model.

For this operation, we will import the data in to Dynamics 365. To import we specifically require data entity, and an adequate dataset match. We also be going through complex data set imports in future blogs. We shall use data management framework to manage data entities and packages in Microsoft Dynamics 365 for Operations.


The data management framework consists of the following concepts:

  • Data entities It represent an underlining table such as Customer or vendor etc.
  • Data project It contains configured data entities, which include mapping and default processing options.
  • Job history Histories of source to staging and staging to target jobs.
  • Data package It contains a data project manifest and used for import or export of multiple files with the manifest.


The import process starts from Import in data management work space which support import of both individual and logically related entities sequenced in correct order.

Import a data package

  1. On the dashboard, click the Data Management workspace.
  2. Click Import tile.
  3. In the Source Data Format field, select TabSeparated and Select ‘Raw material’ as custom data entity. However, one could safely use any standard data entity instead.
  4. Click Upload and select the source data file.
  5. Click View map to generate field mappings.
    Note: Mapping of entities to source is automatics but it also can be overridden.
  6. Locate the tile for the entity in the project, and then click View map.
    Note: A red asterisk (*) identifies any required fields in an entity and must be mapped to work.
  7. Click Mapping visualization on Map source to staging screen.
  8. Define your mapping and click save.
    ss3Note: The entity mapping can be regenerated in the Mapping form if you feel that default appears to be incorrect.
  9. Move to the job screen and click Import.
  10. Execution summary/history will display to the end of execution.
  11. Verify by navigating to the desired form. For instance, in this case Raw Materials details master form.

This is all for


Leave a Reply

Recent Comments