Data Management – Data Export and Import Process – Part 4 (Import Options)

To export data via Data management, you need to create an import job on Workspaces > Data management > Import. You will define a unique “Group name” and then upload a file. This file (e.g. Excel, csv or zipped) should be in accordance with “Source data format” which must have correct mapping describing mapping columns of source file to staging table. This will let D365FO to import column data from source file to staging table.

For example, if you want to import customer groups via Excel, source file should contain correct values for column heading, which can mapped to staging table. To guarantee that the source file has correct mapping, you can export the entity for the company, download it and update it with values that you want to import in the company.

In this regards, you can just fill out the values that you need to import including obligatory fields in the staging table (i.e. CustomerGroupID*).

Then, delete the columns that do not need to import (i.e. this is optional). In this scenario, we create two new customer groups:

On the data import job click on “Add file”, choose source file type, write down the entity name and then upload the file.

Once the source file has been uploaded, it will be indicated on the “Selected” entities. If the source file column name matches staging table, system fulfill the mapping automatically.

If the source file column name partially matches staging table, system fulfill the mapping and “View map” indicate warning triangle and you must fulfilling the mapping source file field to staging table manually.

Thus, click on warning triangle and complete the mapping and click on “Save”.

If you choose a fail source file or choosing a fail entity, you will still get  on view map. There check the “Sheet lookup” to find if you have used correct source file and “View map” to check and complete mapping.

When the source file is a compressed file (i.e. containing source files and xml files for ‘Manifest’ and ‘PackageHeader’), you can upload as package format:

Then the source files will be added and you can control “View map” and “Sheet lookup” and complete the mapping if needed.

Then you have following alternatives as methods for running import job:

Import:  A batch job will be scheduled to run the only once. There will be opened another screen where you can see the result.

Create recurring data job: When you have integration for exchanging data to third-party application/service, you can manage to setup recurrence export job.

Import options > Import now: To run the job synchronously so you get the status of it once it is finished

Import options > Import in batch: To schedule the execution either on recurrence or on later time.

Import options > Re-import: To re-schedule the import job synchronously.

You can find the status of this export job from Job history > Execution details:

Note: Control if you are on correct company before start working with Data management.

Note: If you activate “Truncate entity data”, data entries will be truncated prior to import

Note: It is recommended to use import/export via batch job by assigning a specific batch group to avoid throttling.

Useful links from Microsoft Docs:

Data management overview – Finance & Operations | Dynamics 365 | Microsoft Docs

Recurring integrations – Finance & Operations | Dynamics 365 | Microsoft Docs

Data import and export jobs overview – Finance & Operations | Dynamics 365 | Microsoft Docs

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s