Skip to main content

Upgrading to Dynamics Ax 2012

I have been laying low the past weeks due to some healt problems that have hindered me from working and writing some blogs.

Now I am slowly getting back after an operation on the 31st of August.

Before I went on a sick leave in mid July I was working on an upgrade project from Dynamics Ax 4.0 to Dynamics Ax 2012.

In this first post after the operation I just wanted to point out the importance of the data upgrade process and how important it is for all parties to work to gather to get it done. To success in the process the developer, consultant and the end customer must work as one. As a single unit the developer for example only has few pieces of the puzzle. He or she knows or at least should know how to write data upgrade scripts. But in order to succeed with that the developer needs to know how to transform the data and it is there where the consultant with the end customer come in to the picture.

So togather the consultant and end customer decide how and what data needs to be transformed and the developer knows how to do that.

All the parties involved need at least to have high level understanding of the overall process.

This blog post here from Kevin Kidder is a great help and starting point  http://blogs.msdn.com/b/axsupport/archive/2012/06/04/10266239.aspx

Comments

Popular posts from this blog

Dynamics 365 for operations – Table extensions

Background Extensions are a new way to add functionality and custom code to the D365 system without changing the standard code. In fact, Microsoft has announced that edit standard elements like those that we have done in the past will not be possible after 2017. By using extensions, we can achieve the same result by simply extending the standard system => EXTENSIONS. To read more about the difference between overlaying and extensions follow this link https://ax.help.dynamics.com/en/wiki/customization-overlayering-and-extensions/#extensions Extending tables By using table extensions, we can create a new table that adds new fields, field groups, indexes, mappings, relations, methods, subscribe to event handlers and more. When extending tables we need to follow the naming rule as such: <TABLENAME><_Extension> the compiler understands the _Extensions suffix and knows that the table in question is extending a table from the standard system. This gives us access ...

Remove HTML code from strings

When you work for example with the presentations DAX adds some HTML comment code to the text stored in the database. This can cause the text on the web to be displayed in incorrect format. This also takes up space in the database and makes the database file grow larger. <!--AXAPTA  MarginWidth="0" MarginHeight="0" WebletName="WebLet700062029" Type="WebPageWeblet" -->TEXT There is a nice X++ function: just call Web::stripHTML( string ), which will return the string without the HTML tags