Upgrading tables and EDTs from 2012 is a little different than everything else.

Upgrading code from AX 2012 to D365 can be a daunting task. MS has given us some tools to help but we'll go through a high level overview of the available tools and methodologies to get the process started.

I previously posted on how to install a platform and app update package but got a question: How do you do this if you do not have the tile? I'll briefly walkthrough how to take the long road to installing a PU. Also, unlike my other post, this will be just the PU rather than the PU and app update all in one. Also, I have seen some minor difference between deployments types on app/PU level which may make this look slightly different. I was experiencing this issue with a cloud hosted environment.

Let's walk through how to install a PU plus app update on an LCS slot environment.

Having trouble deploying a 7.3 environment on prem?

Deployment scenarios between AX 2012 and Dynamics 365 For Finance and Operations can now be compared with the on premise version, called Local Business Data, of Dynamics 365 For Finance and Operations, or F&O for short. Below we'll compare and contrast each scenario, sizing, latency, other hidden requirements as well as when you would select Dynamics 365 F&O in Azure or the LBD flavor.

AX 2012 / 2009

When creating the on-premise connector or creating an environment to deploy, want to know where to source all of the values you are being asked for? There are some scripts to help.

Creating The On-premises Connector

Included with the scripts to setup the service fabric cluster is this one:

.\Get-AgentConfiguration.ps1 -ConfigurationFile .\ConfigTemplate.xml

This gives a nice table of output with almost everything you need to create the on-premise connector.