Skip to main content


Showing posts from August, 2012

Inventory dimension fields on reports [AX 2012 Feature pack]

Some minor changes in the feature pack with the way inventory dimension fields are handled in reports. They are now using a map (\Data Dictionary\Maps\InventDimFieldsMap).\ Lets look at an example. I decided to look at the InventTransferOrderOverview report. Notice how populating each InventDim field is now changed to use a map. The way you do the contract hasn’t changed. You use the InventDimViewContract to show the tick box parameters. If you open up the design it uses a column visibility to control if it should be shown. Lets look at the report now.

Naming and number convention for AOS/WSDL [AX 2012]

If you have only one AOS instance, the default port for the root WSDL is 8101. However, if you have multiple AOS instances, the port number depends on which AOS is hosting the services. The WSDL port number is generated by adding the AOS ID to the base port number, which is 8100. You can find the AOS ID by viewing the service name. To view the name, open the Services form in Windows Server, click Start , Administrative Tools , and then click Services . The service name uses the following format: Microsoft Dynamics AX Object Server <version>$<AOSID>-DynamicsAx . For example, the service name that is displayed might be: Microsoft Dynamics AX Object Server 6.0$03 –DynamicsAx . In this case, the port number for the WSDL is 8103. Reference:

Create a custom entity mapping using the Data Migration Framework [AX 2012]

In my last blog post, I went through the steps to using the Data Migration Framework. This post, I will explain the technical side of it. To create a custom entity mapping, click on the Data migration framework > Create a custom entity for migration . Follow the wizard and enter your main table you want to import for. Once the wizard is finished, it will generate an AOT project. To explain the elements: Query The query is a definition of the target table. You could add additional table relationships in there if required for mapping. Table The table suffixed with Entity is the stagging table to use for importing. EDT The foreign key fields using RecId. The EDT generated is a string field representing the code (identification field). Class The class is where we can put your business logic. For example, the EDTs with RecId need to be resolved. The below is a screenshot of a method that takes a string code and finds the related RecId (container is just a standard way o

Step by step import with Data Migration Framework [AX 2012]

Follow the steps on msdn to install the Data Migration Framework. Once you have install, there is also a user guide on msdn but not very detailed. I did my first walk through today and took some notes along the way. There are demo files you should look at. C:\Program Files\Microsoft Dynamics AX 2012 Data Migration Framework (Beta)\DemoFiles\Delimited 1. Click on Data Migration Framework > Setup > Source data formats to set up your source data format. Currently there is on flat file imports available with possible future enhancements from Microsoft to support other types. 2. Under the Applications content, you can select your dimensions. The Dimension code lookup is a multiselection lookup (tick the selection box on the left of the lookup and ok). 3. Click on Data Migration Framework > Common > Processing group. Create a new record and give it a name and descrip