DMF data load using fixed field length files + AX 2012

I have encountered scenario where I need to load data into AX 2012 using fixed field txt files from legacy system. I used DMF to upload the data. The catch is the fixed field txt file upload is different from the regular csv or excel file upload in DMF.

The file format settings will be as follows.


Here we need to perform additional steps to mention the field lengths of various fields and make sure they stay as-is post mapping them to the staging fields.

Once we create the Processing group, Entity record for the required Entity and file format as the one created for Fixed field file, click 'Specify File Format' button and click next.



 
Remove all the field list and add manually the fields from the way they are coming from the fixed length file and also mention the field lengths of the fields.
Click 'Finish'.
 
 
Select the file path where the file for upload is placed on the file system.
Click on Generate Source mapping, this will enable AX to map from file to staging table
Click ‘Modify Source Mapping’ and map the fields mentioned in the mappings sheet ‘FileToStagingMappings’. Once done make sure that the field lengths stay same as above by running the ‘Specify file format’ wizard and selecting ‘No’ in the dialog box.
 
Now we can follow the regular process of Processing Group -> Get Staging Data
to start the data load.
 
Happy daxing :)
 

 
 


Comments

Post a Comment

Popular posts from this blog

Invoicing multiple Sales order using code in AX 2012

Wondering how to post invoice for multiple Sales orders?? Below is the solution. SalesFormLetter salesFormLetter;     QueryRun queryRun;     Query query;     str strSalesTable = "000630,000631,000643";     ;     salesFormLetter = SalesFormLetter::construct(DocumentStatus::Invoice);     query = new Query(QueryStr(SalesUpdate));     query.dataSourceTable(tablenum(SalesTable)).addRange(fieldnum(SalesTable, SalesId)).value(strSalesTable);     queryRun = new QueryRun(query);     salesFormLetter.chooseLinesQuery(queryRun);     salesFormLetter.transDate(systemdateget());     salesFormLetter.specQty(SalesUpdate::All);     salesFormLetter.printFormLetter(true);             salesFormLetter.chooseLines();       salesFormLetter.run();
Read more

Reciprocal exchange rate in same legal entity

Image
In some D365 FinOps implementations, we face scenarios where there is a requirement for reciprocal exchange rate between currencies. Out of the Box, D365 FinOps calculates B to A rate when A to B rate is configured and does not allow set up of B to A when A to B rate is configured. To achieve the requirement, we can make a small customization /extension to allow configuration of exchange rate B to A, while having A to B configured in the same exchange rate type.                                                                                                                                                         ...
Read more

External Code unique value limitation D365FO

Out of the box, D365FO provides External codes feature to capture external references for Customers and Vendors. This could be an external system reference of Customer or Vendor accounts. Standard D365FO External codes data model limits an external code value to be linked to only one account per type - meaning when customer "C0001" has an external code "MemberId" with value "M0001", system will not allow another customer "C0002" to have external code "MemberId" with value "M0001". This limitation is implemented at the table index level. However, there will be scenarios where the business requires same external code value to be allocated to multiple customer accounts. One such is multiple customer accounts linked to one dealer or some businesses having multiple accounts for same customer segregated by state or other criteria. In such cases, the out of the box index limitation will not allow same external code value to be alloca...
Read more