Convert Field Values During The Importing Process Through DIXF

In the last two articles we discussed how to:

• Configure DIXF To Automatically Generate Unique Key Using Number Sequence.
• Assign Default Values Automatically During the importing process through DIXF.

Today we will discuss how we can convert the field values during the importing process.

Sometimes we may need to convert some of the master data values, especially when we planing to import data from a legacy to new system. For example, assume that one of your clients request to reclassify the vendors from a business line to a new one. in this case you can set up DIXF to convert the old business line value to the new value instead of change the business line for these vendors manually.

The following example we'll show how to convert the Vendor Line of Business during data import process.However we can use the same approach to change the values for any other fields.

Assign Default Values Automatically During the importing process through DIXF

During the preparation to import data, we often find ourselves having to fill a lot of values that are often the default values. For example, language, currency, customer group or group of suppliers etc....

In this article i will show you how we can assign default values during the importing process through DIXF.

The following example illustrate how to automatically assign default values for vendor currency and vendor group during the importing process. However we can use the same approach to assign default values for any other fields.

Configure DIXF To Automatically Generate Unique Key Using Number Sequence

Do we really need to manually add the reference numbers in the source file when we planning to importing data through the Data import export framework ? No we don't need to do that anymore :)

In this article i will show you how we can Configure DIXF to automatically generate unique key using number sequence during the importing process.

The following example illustrate how to generate vendor accounts automatically during the importing process. However we can use the same approach to generate the unique key for any entities.

Importing purchase orders using DIXF

In this post we will illustrate how to import purchase orders through data import export framework. we will use one excel file which contain purchase order header in first sheet and purchase order details in another sheet.


to import the purchase order please do the following steps:

AX 2012 | Import Released products using DIXF

This post illustrate how to import released products using the data import export framework in Dynamics AX 2012. We are going to import some of the released products information, you can add or remove fields as needed.

To import the released products please follow the steps below :

AX 2012 | moving average costing method - Part 4

In this part we will discuss production costing with moving average. If you use moving average in production costing, costs can be based on the current costs of raw materials rather than on the cost price that was originally registered for the item master. When the finished good is reported as finished, the cost reflects the estimated product cost calculation that is executed by a release of production orders.

The original cost calculation of the finished good might have happened months ago, and thus it might be outdated. With moving average, the result of a product cost calculation that is executed during the estimation process can be adopted rather than the cost from the original cost calculation of the finished good.

AX 2012 | moving average costing method - Part 5

This is the last part of the  moving average costing method in Dynamics AX 2012. in this part we will discuss the reports which show how moving average was calculated.

If you sort transactions on the inventory value report according to transaction time, transactions are listed chronologically, and you can view the costs from a moving average perspective. This way, you can verify that the cost of a moving average product has not been changed retroactively, even though the product has, for example, been adjusted by using backdating.

AX 2012 | moving average costing method - Part 3

After we discussed the Handling of price differences between a product receipt and the invoice in part 1 and Revaluation for moving average in part 2. in this post we will discuss the Backdating with moving average.

When you backdate a product receipt or an invoice, it is revalued to the current moving average cost. Also, a backdated issue is posted at the current moving average cost. With backdating, you cannot change the moving average going forward.

AX 2012 | moving average costing method - Part 2

In part 1 we discussed how to set up moving average costing method, then we discussed  how moving average is handling of price differences between a product receipt and the vendor invoice.

Today we are going to learn how to revaluate cost for moving average. To proceed with the next example you must read part 1 of this series or at least do the setup which described there.

If your moving average value is inaccurate because of, for example, a posting mistake, you can adjust the unit price of the on-hand inventory at any time.

The moving average cost can only be adjusted as of the current date, so when you adjust the unit price of an item by using the following procedure, the adjustment date is always set to the current date. You cannot change the date when you post the adjustment.

AX 2012 | moving average costing method - Part 1

In this series we are going to discuss the moving average costing method, by covering the following topics:

Part 1: Handling of price differences between a product receipt and the invoice.
Part 2: Revaluation for moving average.
Part 3: Backdating and moving average.
part 4: Production costing and moving average.
part 5: View how moving average was calculated.

first let's introduce the moving average costing method. Moving average is an inventory evaluation method that reevaluates inventory value in the chronological order of posting transactions, and it can be used to compute the average cost of the current ending inventory.

When a receipt transactions are included chronologically in the moving average calculation, according to the order in which the transactions are recorded in the system.

When Issue transactions are assigned the current active moving average cost at the time of recording, and the costs on inventory issues do not change even if the purchase costs (price in vendor Invoice ) change.