Microsoft Dynamics AX 2012 Data Import Export Framework Integrations Using DMFLedgerBalanceEntity
The Data Import Export Framework offers a DMF class called DMFLedgerBalanceEntity as a basis for integrating, from an Excel source file, unposted journals into Dynamics AX 2012 R2. We've used this DMF class significantly over the past several weeks on integrations from a variety of different fronts. As part of testing and using this DMF class for integrations into unposted journals, we've regularly used the Data Import Export Framework Execution History as a basis point for reviewing any potential errors or problems found during the integration. The Data Import Export Framework Execution History typically does an effective job of pointing out where the problem resides and can be quite helpful with reviewing the results of integrations. Based on experiences encountered with using the DMFLedgerBalanceEntity class for running Data Import Export Framework integrations, I've accumulated a list of some errors that you can encounter in the Execution History and some detail around what the error messages mean. Understanding the reasons for what you'd see in the Execution History from running various Data Import Export Framework integrations should help you better understand the tool.
Common errors that could be found in the Data Import Export Framework Execution History when using the DMFLedgerBalanceEntity class for integrating into the context of unposted journals in Dynamics AX 2012 R2:
1. You receive the following error message when you attempt to perform the Copy data to Target step of processing: "Main account should be in the first segment."
a. What it means: This means that there is a Main account in a Main account segment in a LEDGERDIMENSION/OFFSETLEDGERDIMENSION field of the source file where one of the following is true:
- The Main account flat-out does not exist in Dynamics AX 2012 R2; or
- The Main account exists in Dynamics AX 2012 R2, but does not exist in the legal entity's account structures for which you are running the integration into.
2. You receive the following error message when you attempt to perform the Copy data to Target step of processing: "Financial dimension does not exist."
a. What it means: This means that there is a Financial dimension value in a LEDGERDIMENSION/OFFSETLEDGERDIMENSION field of the source file where one of the following is true:
- The Financial dimension value does not exist in Dynamics AX 2012 R2; or
- The Financial dimension value does not exist in the legal entity's account structure for which you are running the integration into.
3. You receive the following error message when you attempt to use the Get staging data button in processing: "Unable to open file."
a. What it means: This means that the Excel source file is currently open at the time that you run the integration. You cannot have the Excel source file open at the time that you run an integration.
4. You receive the following error message when you attempt to use the Get staging data button in processing: "Cannot execute the required database operation. The SQL database has issued an error. SQL error description: {Microsoft}{SQL Server Native Client 10.0}{SQL Server} Error converting data type varchar to bigint. SQL statement: UPDATE DMFLEDGERJOURNALTABLEENTITY set VOUCHER = .FN_FMT_NUMBERSEQUENCE. Issue exists in generate staging data."
a. What it means: This means that Data Import Export Framework doesn't like the Cell Formatting of the JournalNum column in Excel.
- Go to the Excel source file, right-click on the JournalNum column, and click Format Cells. In the Cell Formatting, change the Type to 'Text', and then re-save the Excel .csv file.
Under the terms of this license, you are authorized to share and redistribute the content across various mediums, subject to adherence to the specified conditions: you must provide proper attribution to Stoneridge as the original creator in a manner that does not imply their endorsement of your use, the material is to be utilized solely for non-commercial purposes, and alterations, modifications, or derivative works based on the original material are strictly prohibited.
Responsibility rests with the licensee to ensure that their use of the material does not violate any other rights.