‘Debit’ is ‘DebitAmount’ and so on and so forth. For example, the ‘Account’ field in general journal lines is called ‘AccountDisplayValue’ field for importing purposes. This allows you to get through a lot of the leg work of deciding which fields you may need and what is the actual field name. Simply compare the file to the actual form in the system to determine which fields you may need and delete the ones you don’t. The file generated will provide you with all the D365 fields and the data from the system. Once the file has been exported, click Download package at the top of the form. When ready click the Export button at the top of the form. Configure the export job and choose the data entity that you want to import to later. In the data management form, choose the Export job. However, there is an easier way to ensure your mapping is correct the first time around. In that form, you can manually connect the lines from your header fields to the D365 fields.
During your initial setup of the import job, you can see which fields were mapped incorrectly by clicking the View map button. Occasionally, you may get an error that some of the fields are not correctly mapped. This next tip should make your life just a little bit easier. In the general journals form, you can see the journal batch number generated automatically and the import came in one batch. Additionally, this will ensure that every line in this file is imported under the same batch. As you can see in the image below, I have included the journal batch number header, but the contents of that column are empty. However, even though you need the field in your import file, you don’t need to put any data in the column because D365 will automatically generate the journal batch number. If you are importing any kind of journal, this field is necessary. The first tip I want to mention is regarding the journal batch number field. For the final part of this series, we will discuss tips in preparing your data management imports. In the first blog, we discussed configuration and in the second blog, I gave examples of common errors and how to troubleshoot them. Welcome back for the final installment of this blog series on data management in Dynamics 365 for Finance and Operations. Posted on: J| By: Jarrod Kraemer | Microsoft Dynamics AX/365 Data Management Importing Tips for D365 for Finance and Operations: Part 3
0 kommentar(er)
