How to Install and Configure Dynamics AX 2012 Components Over the past few weeks, I was involved in installing and configuring Dynamics AX 2012 Components on couple of machines running Server 2008 and Windows 7 Enterprise O/S.

Is there some way that I be able to know which functionalities are related to a hotfix installed in Dynamics AX? Normally the hotfix comes with a list of modified/added objects (which I can create unit tests to it) but not with a list of modified/added functionalities, which is what I need. How do you guys normally test a hotfix?

Alex Kwitny

2 Answers

You could look into the customer/partner source -

As my company is gold partner we receive each month a list with hotfixes, that describe the functionalities changes, so maybe you could receive same list if you contact your regional Microsoft contact.

UPDATE:

From here:https://msdnshared.blob.core.windows.net/media/2016/07/DynamicsAXLatestHotfixList20160701.xlsxYou can download a list with hotfixes and short description.For KB3161035 - CDCR - Financial dimensions for Transfer Orders (TO)

The hotfix package that you provided has many more models that you actually need.Look in the Hotfixinformation.xml there should be information which models you need for KB 3161035.When searching in the file found that:KB='3161035' - needs only model: AxModel ModelId='4568521'

So you could cut all other models files from folder /models/ and leave inside the folder only ModelId='4568521' and syp labels. Then install the hotfix.

That way you could test only the functionality you need CDCR - Financial dimensions for Transfer Orders

Best Regards,Kristian

Hotfixes are usually delivered as a module. To create a project with the elements affected:

1. ToolsModel managementModels installed - find the model by sorting in reverse number
2. ToolsModel managementCreate project from model - lookup the same model

Hotfixes are testet by having a failing testcase before the install, then installing, then reapplying the test after install (hopefully succesful). In an ideal world you would have two identical systems (application and data), then apply the hotfix to one of them.

Run the impact analysis before installing as explained here.

Jan B. KjeldsenJan B. Kjeldsen

Not the answer you're looking for? Browse other questions tagged axaptadynamics-ax-2012hotfix or ask your own question.

-->

This topic explains how to set up the Data migration tool (DMT) so that you can migrate data from Microsoft Dynamics AX 2009 to Microsoft Dynamics 365 for Finance and Operations.

Important

At this time, the DMT is in private preview. If you are interested you can sign up for the Preview Program. The public release date for the DMT has not been set.

Prerequisites

• Microsoft SQL Server 2008/2012/2014/2016.

• The Microsoft .NET Framework version 4.5 or later.

• Microsoft SQL Server machine that has Microsoft SQL 2012 Native Client installed.

• The Microsoft SQL Server Integration Services (SSIS) service is installed and running on the machine where the DMT service will be installed.

• SQL Server authentication must support both SQL authentication and Microsoft Windows authentication.

• Microsoft Access database engines that follows the version guidance in the following table.

  SQL Server 2008	SQL Server 2012 and later
  No Microsoft Office on the VM	Access engine 32-bit	Access engine 64-bit
  Microsoft Office 32-bit	Access engine 32-bit	Access engine 64-bit
  Microsoft Office 64-bit	Access engine 32-bit and 64-bit	Access engine 64-bit

• Microsoft Dynamics AX 2009 SP1 5.0.1000.52 or later.

• The prerequisite patch (axpatch.exe) installed. To find the patch, from the location where you downloaded and extracted the zip file, go to <pre-requisiteforpatch><application>.

Install DIXF service

1. Go to the location where you extracted the zip file, and then, in the DIXF msi folder, right-click DIXF_Service_x64.msi, and select Run.
2. When the wizard starts, select Next.
3. Accept the license terms, and then select Next.
4. Select an account for the service, and then select Next. The account should have admin rights. If you select the Network Service check box, verify that the network service account has admin rights. Otherwise, clear the check box, and enter an admin account user name and password. Then select Next.
5. Select the SQL Server version, and then select Next.
6. Select Install, and then, when the wizard is completed, select Finish.

Copy binaries

Go to the location where you extracted the zip file, and copy the following files to the Program Files (x86)Microsoft Dynamics AX50ClientBin folder:

• Microsoft.Dynamics.AX.Framework.Tools.DMT.dll
• Interop.Shell32.dll

Install DMT components for AX 2009

There are two ways to install the DMT. You can use the combined XPO file or an application hotfix. If you're using a Microsoft Dynamics Lifecycle Services (LCS) Implementation project, use the application hotfix. Installation takes approximately seven hours.

Combined XPO file

1. Extract the combined XPO file from DMT_V1.0CombinedXPO.
2. Import the combined XPO file into AX 2009.
3. Copy the label file from DMT_V1.0Label file to the Program FilesMicrosoft Dynamics AX50ApplicationAppl<NameOfYourDeployment> folder.
4. Restart the Application Object Server (AOS) instance.
5. In AX 2009, select Data migration > Setup > Compile and synchronize DMT application.

Note that the combined XPO file is imported into the layer that the user is signed in to.

Application hotfix

1. Go to DMT_V1.0ApplicationHotfixDynamicsAX2009-KB4010403-SP1, right-click setup.exe, and then select Run.
2. In AX 2009, in the Application Object Tree (AOT), notice that the LegalEntityId field has been added to the DMTCustomerAddressView and DMTVendorAddressView views.
3. Select Data migration > Setup > Compile and synchronize DMT application.

Parameter setup

Go to the location to where you extracted the zip file, and find defaultvalue.xlsx.

Note

The file is saved in .xlsx format. Don't change the extension. When you provide this file as input for the Default configuration parameter, select All Files so that you can select the .xlsx format. If you don't select this format, errors will occur when you start to generate mappings.

1. In AX 2009, select Data migration > Setup > Configure default maps, and enter the appropriate information in the following fields:

   • Default configuration – Enter the path of the Microsoft Excel file.
   • Export file path – Enter the server path that can be accessed by the service.
   • SQL Server user and password – Enter the SQL authentication credentials for the AX 2009 database.

2. Close the form.

3. Under Setup, select Configure connections, and enter the appropriate information on the following fields:

   • DIXF service host – Enter the host name of the DIXF service installation.
   • Tenant URL – Enter the Finance and Operations URL. If you aren't sure of the tenant, see the Finance and Operations web.config file.

   [!NOTE}In the Azure Portal, when you create a new app in the Azure Active Directory (AAD), you can select from two options. Web API and Native. In this instance, select Native and grant permissions to native AAD app.

What Is Microsoft Dynamics Ax

How To Install A Microsoft Bluetooth Keyboard

Multi-box setup

For a multi-box setup, you must have the following machines:

• Machine A, where the AX 2009 database and DIXF service are installed
• Machine B, where the AX 2009 AOS instance is installed
• Machine C, where the AX 2009 client is installed

In this three-machine setup, machine C is configured to connect to the AOS instance on machine B. Machine B is connected to the database that is configured on machine A.

DIXF service machine prerequisites (machine A)

The DIXF service on machine A has the following prerequisites:

• SQL Server 2008/2012/2014

• The .NET Framework version 4.5

• Access database engines

  • For SQL Server 2008: Access engine 32-bit and 64-bit (if Microsoft Excel is 64-bit)
  • For SQL Server 2012 or later: Access engine 64-bit

• AX 2009 database (configured on SQL Server)

AOS machine prerequisites (machine B)

How To Install A Microsoft Dynamics Ax Hotfix Tool Download

The AOS installation on machine B has the following prerequisites:

• AX 2009 AOS Server
• Application files

Client machine prerequisites (machine C)

The client installation on machine C has the following prerequisites:

• AX 2009 client

Shared folder permissions

The path of the default configuration file and the export package file should be shared, and client users and the DIXF service should have read/write access to these files. To grant this access, select Data migration > Setup > Configure and generate maps, and then select Validate path to verify that the required access is available.

Set up parameters

1. Select Data migration > Setup > Configure connections.
2. In the DIXF service host field, enter the name of the remote machine where the DIXF service is installed. By default, the name is localhost.
3. Select Validate to validate that the client can access the DIXF service.

Workarounds

If you receive an error message that states, 'DIXF service is unavailable,' complete the following workaround to enable a service connection for port 7000.

1. Open port 7000, and then, for inbound rules on the DMT service machine, select Firewall settings, and then select Run > wf.msc.
2. Select Inbound Rules > New rule, and then, on the Rule Type tab, select Port, and then select Next.
3. In the Specific local ports field, enter 7000, and then select Next.
4. Select Allow the connection, and then select Next.
5. Select all three check boxes to apply all the rules, and then select Next.
6. Enter the name of the rule, and then select Finish.
7. Repeat these steps for outbound rules.