Learn how data management works in Microsoft Dynamics 365 for Finance and Operations by following the below guidelines for importing and exporting data, batching large files and troubleshooting error messages. Also read some helpful tips for loading data through LCS (lifecycle services) configuration and data manager.

How does Data Management work in Dynamics 365 for Finance & Operations?

Data Management Workspace

Import

1. Use file format created by exporting an entity or group of entities
2. Check which fields are mandatory by checking the mapping of the entity
3. Remove non-essential columns from import file to reduce potential for errors during upload

Export

1. Recommended for creating the blank or sample data packages/files for import
2. Exports can be filtered to include specific data

Templates

1. Create Templates to group together dependent import forms
2. Select an Entity to see which other entities it is dependent upon

Configure Data Source

1. Several standard data sources are set up – excel, CSV, xml, etc.
2. Additional data sources can be set up if required (useful for linking to external databases for recurring imports/exports)

Configure Entity Export to Database

1. Used for publishing data to an external database for things like BI tools

Data Entities

1. List of available entities:
   • Entities contain fields that can be filled in for importing information
   • There are hundreds of entities but they don’t cover 100% of all tables of all modules. Some may need to be created.
   • What happens when an entity doesn’t exist out-of-the-box? Developers can create a custom entity or combination of entities using Visual Studios.
2. Includes Staging table and Target entity information

Framework Parameters

1. Data management settings

Staging Cleanup

1. Clean up job history

Set up Roles for Data Projects

1. Security to allow/deny access to certain data projects

Batching Large File Imports and Exports

1. Very Large Imports can be set to Import or Export in a Batch

Sequencing

1. The order of loading data packages is important due to dependencies within the file.

Parameter, reference, master, document, transaction

1. Data packages will fail if setup information is missing.
2. Templates section enables you to easily check an entity to see which information it is dependent upon.  For example, bank accounts require a currency. Currencies need to be set up before bank accounts can be fully set up.

Notes

1. After importing an Excel file, make sure that data management is closed before reopening the Excel file or it may become corrupted and unusable.
   • Recommend ‘save-as’ new file name before importing to preserve the import file.
2. When importing open customer invoices, we previously ran into an issue where extra ‘remit-to’ addresses were created for each customer. Hundreds of extra addresses were created.
3. To find which entity belongs to a form, right click on the form to get the form name

Troubleshooting Error Messages

1. Most errors will be due to invalid data in the import file or missing setup information
2. View staging data
   • Some errors can be corrected in here and uploaded
3. View execution log
   • Staging log details
   • Infolog
   • View error file

Loading Data Through LCS Configuration & Data Manager

Microsoft recommends, but does not require, that users load data through LCS

1. If data is loaded through LCS, and there are issues, it is easier for Microsoft to support.
2. It makes it easier to deploy the same packages to multiple environments.
3. It’s useful if there is more than one person loading packages.
4. Complete upload history is in one place for easy review.

If you have any questions about Dynamics 365 for Operations, please feel free to get in touch with us.