Install an application x++ hotfix [AX7]

Microsoft has document this well on the wiki but can be confusing for first time. Also, things are improving and sometimes hard to keep up.

This is what you see on LCS when updates are available.

This wiki page walks you through the steps for applying a Microsoft Dynamics AX deployable package on a Dynamics AX system. This package can be either a binary hotfix for Application Object Server (AOS) or a deployable package that was created in your development environment.

Apply a deployable package on a Dynamics AX system

https://ax.help.dynamics.com/en/wiki/apply-a-deployable-package-on-a-dynamics-ax-system/

The most misunderstood part is the application x++ updates. What you are downloading from LCS is the x++ code. You are not downloading a deployable packages. A deployable package is a compile output that you can use to install to your none development machines.

Below link guides you how to install it.

Install a metadata hotfix

https://ax.help.dynamics.com/en/wiki/configuring-and-installing-a-metadata-hotfix-package/

Below is how you do it using the visual studio addin rather than command line. Saves you a bit of time.

Click on Addins > Apply Hotfix

It defaults the parameters but you have to browse and select your file.

Visual studio will try to process. You can see Task manager to see that it has kicked it off.

It may take a few minutes but you will get a message.

Check that it has been applied.

Important:

• Addins can change at any time. So, learn the proper way from the Microsoft Wikis. Know what it is doing.
• You can create your own addins to improve tooling. That is why Visual studio is so great.

Install an application x++ hotfix [AX7]

Microsoft has document this well on the wiki but can be confusing for first time. Also, things are improving and sometimes hard to keep up.

This is what you see on LCS when updates are available.

This wiki page walks you through the steps for applying a Microsoft Dynamics AX deployable package on a Dynamics AX system. This package can be either a binary hotfix for Application Object Server (AOS) or a deployable package that was created in your development environment.

Apply a deployable package on a Dynamics AX system

https://ax.help.dynamics.com/en/wiki/apply-a-deployable-package-on-a-dynamics-ax-system/

The most misunderstood part is the application x++ updates. What you are downloading from LCS is the x++ code. You are not downloading a deployable packages. A deployable package is a compile output that you can use to install to your none development machines.

Below link guides you how to install it.

Install a metadata hotfix

https://ax.help.dynamics.com/en/wiki/configuring-and-installing-a-metadata-hotfix-package/

Below is how you do it using the visual studio addin rather than command line. Saves you a bit of time.

Click on Addins > Apply Hotfix

It defaults the parameters but you have to browse and select your file.

Visual studio will try to process. You can see Task manager to see that it has kicked it off.

It may take a few minutes but you will get a message.

Check that it has been applied.

Important:

• Addins can change at any time. So, learn the proper way from the Microsoft Wikis. Know what it is doing.
• You can create your own addins to improve tooling. That is why Visual studio is so great.

AX 7 Working with Version control

This is the landing page for setting up your development environment with version control.

https://ax.help.dynamics.com/en/wiki/using-development-tools-in-ax7/

This is relatively easy and setting up a new solution/project works without a problem. In this post,I want to highlight a little gotcha. If you open up a solution and notice the project isn’t bound to version control. i.e. No padlock icon, not able to check out

Then it looks like you may have to bind the solution. Open up the solution using source control explorer. You should get this message asking you to bind it. Click on Yes and follow it.

Following screen you get.

Otherwise, create a new solution that and make sure to tick the “Add to version control” flag in the dialog.

AX 7 Working with Version control

This is the landing page for setting up your development environment with version control.

https://ax.help.dynamics.com/en/wiki/using-development-tools-in-ax7/

This is relatively easy and setting up a new solution/project works without a problem. In this post,I want to highlight a little gotcha. If you open up a solution and notice the project isn’t bound to version control. i.e. No padlock icon, not able to check out

Then it looks like you may have to bind the solution. Open up the solution using source control explorer. You should get this message asking you to bind it. Click on Yes and follow it.

Following screen you get.

Otherwise, create a new solution that and make sure to tick the “Add to version control” flag in the dialog.

Dynamics AX 7 Development I – Create a model

With the recent release of AX7 CTP8 public preview there are a lot of things to learn. I thought I would do some basic series of tutorials to explain a few concepts and how to get around for developers.

In this first one I will explain how to create a model.

Click on Dynamics AX > Model Management > Create model

Follow the wizard by entering a name and a publisher

This is very important if you want to create extensions or if you want to customise existing functionality by over-layering (which we try to avoid as much as we can).

After you finished you can create a new project in that model.

In the Application Explorer there are two views

• Model View – Shows the AOT divided into its models. Each model has its own subset of the AOT (elements that belong in the model)
• Classic View – Shows a single AOT classic view we are used to

You will notice in the Packages folder that the model folder was created under the application suite.

Good reference material available under the wiki site

https://ax.help.dynamics.com

Dynamics AX 7 Development I – Create a model

With the recent release of AX7 CTP8 public preview there are a lot of things to learn. I thought I would do some basic series of tutorials to explain a few concepts and how to get around for developers.

In this first one I will explain how to create a model.

Click on Dynamics AX > Model Management > Create model

Follow the wizard by entering a name and a publisher

This is very important if you want to create extensions or if you want to customise existing functionality by over-layering (which we try to avoid as much as we can).

After you finished you can create a new project in that model.

In the Application Explorer there are two views

• Model View – Shows the AOT divided into its models. Each model has its own subset of the AOT (elements that belong in the model)
• Classic View – Shows a single AOT classic view we are used to

You will notice in the Packages folder that the model folder was created under the application suite.

Good reference material available under the wiki site

https://ax.help.dynamics.com