Adopt the Microsoft Dynamics AX 2012 Feature Pack - a must have

Recently, in February of this year Microsoft released the Microsoft Dynamics AX 2012 feature pack. You can access the latest Dynamics AX ISO, which includes the feature pack, from the following location on PartnerSource: Microsoft Dynamics AX 2012 Feature Pack Release.

From the release notes: "Microsoft Dynamics AX 2012 Feature Pack is the Microsoft ERP solution for enterprises that empowers your people to anticipate and embrace change so your business can thrive. It constitutes our biggest releases that target five key industries: Manufacturing, Distribution, Services Industries, Public Sector, and Retail. This release also incorporates Microsoft Dynamics ERP RapidStart Services.

All of the industry solutions, Process Industries, Public Sector, Retail, and Service Industries, are now incorporated into the product and are installed the same way as other Microsoft Dynamics AX modules. Customers can enable or disable features by using configuration keys and can use features from multiple industry solutions. For example, a Public Sector organization can use the Retail POS capabilities, a pharmaceutical company involved in drug discovery and trials can use Service Industries and Process Manufacturing capabilities, or a wholesale distributor can use the Retail merchandising features."

Further, Microsoft just recently as of three days ago posted the following link on PartnerSource stating: "We strongly recommend that all Microsoft Dynamics AX 2012 implementations move to using the Feature Pack"

The Resource Page.: The Microsoft Dynamics AX 2012 Feature Pack—Why You Should Adopt it Moving Forward

There are several reasons to make sure that the feature pack is the focus now and moving forward from all the updates to specific industry solutions adding retail, if desired, as well as having now support for 25 Countries. Further, Microsoft points out that: "When Microsoft Dynamics AX 2012 R2 is released in H1 Calendar Year 2013 it will automatically install the remaining Microsoft provided country localizations (Asia, South America, Eastern Europe, etc.); so that we maintain the single consistent Microsoft Dynamics AX 2012 code base."

This then suggest, that in order to go to R2 - with the least time needed for deployment, having what resides in the feature pack for Microsoft Dynamics AX 2012 is a critical step. Further, applying and using the feature pack as the target version for any and all current AX 2012 instances, gives you the same build as CU2. Bringing your Microsoft Dynamics AX investment to the latest and most stable build. Even if you have applied CU2, you should look towards the feature pack, as it's clear through the message it's a stepping stone towards R2 that will be release first half of 2013.

Well that's all for now, check back soon though as a whole lot more to come. Till Next Time!
Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

Code Upgrade Service for Microsoft Dynamics AX 2012

Welcome to the year 2012 everyone! I hope that you all have a blessed and very successful year, and that 2012 is your best year yet! To kick off this year, I thought I would focus the first blog post, around InformationSource and specifically the Services section of InformationSource.



Within InformationSource, once you sign in either with your PartnerSource or CustomerSource enabled windows live id, there is a section called Services. Within this section there are several tools, all beta, that have been released in order to help you with your AX 2012 projects. Recently, I highlighted one of these, the IDMF, or Intelligent Data Management Framework for Dynamics AX 2012. Today, I wanted to switch focus now, and look into another tool, the Code Upgrade Service for Microsoft Dynamics AX 2012.

Direct from InformationSource about the Code Upgrade Service:
"This service is designed to help Microsoft Dynamics AX developers upgrade their X++ code to Microsoft Dynamics AX 2012. the service analyzes X++ code patterns and automatically fixes some patterns, provides suggestions on how to fix other patterns, categorizes upgrade task, and enables developers to add their own patterns to be analyzed."

Further, the following is from the short screen cast on InformationSource, about the focus and intent of this new tool.



As you can tell, the idea behind this great new Service, is around helping companies with their upgrade projects, and specifically focused around the code investments / customizations that a specific company has made within their Dynamics AX instance. Now I must state again, all of these tools are currently in Beta, so use with caution, and understand this fact. To help better understand how to use this new tool, Microsoft has a home page on TechNet, specifically for the Code Upgrade Service.: Code Upgrade Tool User Guide [AX 2012]

There are several sections, to the current Beta release of the User guide, that cover:

• Install the Code Upgrade Tool
• Run the Code Upgrade Tool
• Extend the Code Upgrade Tool
• Uninstall the Code Upgrade Tool

In a nutshell, the code upgrade tool is an AX 2012 model file, called "Code Upgrade Tool Model.axmodel". There are also several Managed code assemblies that are delivered as part of this tool. Specifically these assemblies contain the out-of-the-box rules, listed in the following categories:

• AddressBook - Rules that are related to adoption of the updated address book framework for Microsoft Dynamics AX 2012
• FormLetter - Rules that are related to adoption of the updated form letter framework for Microsoft Dynamics AX 2012
• IDGoAway - Rules that are related to adoption of the updated type IDs
• Inventory - Rules that are related to adoption of the updated inventory refactoring in Microsoft Dynamics AX 2012
• Number sequence framework - Rules that are related to adoption of the updated number sequence framework for Microsoft Dynamics AX 2012
• XppCompiler - Rules that are related to adoption of compiler changes.

After installing, its highly recommended that you experiment with the tool, and see what kind of errors it can identify, as well as fix. It comes then, with two example classes:

• PipelinableMutator, which contains errors that the tool can identify and fix.
• PipelinableSweeper - which contains errors that the tool can identify, but can not automatically fix for you.

Once you get a feel for how to use the tool, and the value it can add to your upgrade process, keep in mind that from the ISV, VAR and Customer level, the tool is meant to be extended. Make sure that before you attempt to extend the tool, that you read carefully the section on extending the Code Upgrade Tool.

Well, that's all for now. Hopefully this is a great introduction for you, and you can start using this tool, to help with your projects today. Finally, stay tuned, as there is a lot of topics to cover about the Dynamics Ecosystem, Dynamics AX 2012, and a whole lot more. Till Next Time!

Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

AX 2012 - Upgrade Questions Answered

Recently, I took part in a community effort, in order to drive awareness, as well as social connections for the Dynamics Community. This experiment, was focused around the Microsoft Community Site, hosted a set of questions around AX 2012 Upgrades.

Several people took part in this, for submitting questions, and giving answers. The following link, will guide you to this first iteration of such an effort: Microsoft Dynamics Community: Dynamics AX 2012 Upgrade Questions……Answered!

An Example, from this post, can be seen here:
"Community Question #1

First of all I want to say I love the initiative! Great to see that Microsoft is working pro-active! My question is related to the licenses. There will be different type of roles which will play a part in the license value for a given customer. Image I have a lot of project manager which will be functional roles. Are there any limitations regarding availability of different legal entities? With other words, can a functional user use/see all the legal entities deployed in an AX2012 application?

What about custom security roles made by the partners? How will they fit into the license layout..."

And the answer I provided:
"First, lets address the fact that AX 2012 License model has changed a lot actually. It's for sure a much simpler approach, and closer to how Microsoft license it's other products for use. The best source, to help understand the new license model, in full can be found from the following PDF, white paper guide: Download Whitepaper

With this in mind, it's very clear that the mappings of named user types, to menu functions, and therefore roles will have to be updated. For example, currently, if you basically touch anything with a journal, for updating say, then your user will be marked as an Enterprise Named User License. This is not the vision Microsoft had for this, so there is a planned revisit to get the menu functions, and therefore ultimate mapping of users to Named User Types updated.

With that knowledge in hand, lets move to the more direct question, is the ability to cross legal entities for performing work. This is clearly stated as a goal, if a user is meant to cross legal entities they will be considered an Enterprise Named User. That make sense, in that, if your crossing legal entities, you are no longer a Functional or Task user, because you are truly doing functions at the enterprise level.

Finally, lets address your question around custom roles and security. In terms of reference to the Named User types, when custom menu functions, and business logic is created, either via an ISV, or the customer itself, the Microsoft Named User license count is not affected. If you look, for example, and create a custom menu item, which is how the Named User counts are tallied and linked, you will notice that None is set, instead of Functional, Task, Enterprise, etc. To the license point for ISV there is a different license model that ISV's can use, that for a customer will have to maintain that either through their VAR, or through a direct relationship with the ISV who is providing you service.

One note, I will make about this, is around AX in the cloud. When this is the approach, and the Partner Hosted model is in place, you pay by month, per user. The named user license still can come into play, however you only upcharge, if you will, when you add another user. So for example, if your implementing AX, via the cloud, and only need 5 users at first to get the implementation going, that's all you will be billed for, in the months those five users access your instance. When the next month rolls around, and say you add a cost accountant, for working in your AX implementation. Then this will add a sixth user license count and from that month forward is when you will pay the difference added to your bill for that use."

I would like to thank Andy, and the team at Microsoft for allowing me to take part in this effort. I look forward to such future engagements, as I believe this really helps connect the community. Using the power of social media, to get real world questions, answers and the sharing of knowledge.

If you have a burning question, feel free to leave me a comment on my blog, email me, and of course let Andy at the Microsoft Community Know. It could help shape the next topic, for when we do such an effort in the future.

That's all for now, but check back soon as more to come! Till Next time!

Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

AX 2012 - Understanding the changes to Table Relations

Well I hope everyone is having a fine week so far. Oh Wednesdays, the furthermost point between two weekends. It's a day of great productivity, as we push towards that glimpse, and hope for our Saturday and Sunday.

To help you out during the middle of this week, I thought it was time we spent a little focus around the changes in AX 2012 around extended data types, and specifically around understanding the way relations are made.

First off the bat, lets look to the Extended Data Types in the Database [AX 2012] In this article on MSDN, Microsoft points out some highlights about EDT's in AX 2012, specifically, highlighted is:


"Starting in Microsoft Dynamics AX 2012, you can no longer define relations under an EDT element in the AOT. If your system has any EDT relations, you should migrate those relations to the appropriate table elements. For more information, see EDT Relation Migration Tool."

On this same page, before we move forward in looking at what this means, there is a link on How to: add Dimensions. Make sure to NOT follow that link. It has not been updated yet for AX 2012.

Now with that aside, lets look at what this means for AX 2012. Back in AX 2009, relations would exist, on the EDT, for example, linking a specific EDT, to a reference table, in which the EDT was the primary key.

Now in AX 2012, this has moved to the table relations level. So lets take the following for example. If I have a Table, and as part of it, I would like to have an EDT, that is controlled and is referenced to an underlying table itself. This EDT then, and the field that it represents would be a foreign key for this new table we are building.

To help set this straight, lets look at the following.:


With this, we have the relationship, that now lives at the Primary Table, that has a Foreign Key, represented by the EDT. The EDT, in turn is the Primary Key, for the underlying reference table.

Moving ahead, lets see this in action, with a simple example. To see this in action, we will need a project, an Extended Datatype, or EDT, as well as our reference and Primary table.



You will notice that I have already added the EDT, as the PrimaryField to the idbReference Table node. Also, I've created a Primary Index, and placed that field in the Primary Index, as set the index to not allow duplicates.

Now that we have this base, we must move to the EDT, and add the idbReference, as a table reference to the EDT. This does not set the relation, instead it is the primary reference for the EDT.





After this, we add the EDT, to the Primary table, which I've called ForeignKeyField, in order to help understand the point.



Now that we have this, we next have to create our relation, from the Primary table to the reference table. We do this, and on the properties of the relation, we set that it's an EDTRelation = Yes.



In doing this, we can now set the relation, via a Normal Relation Option, from our Primary Table, to our Reference Table field. In doing this, and because of the EDTRelation = Yes is true, we can now select what EDT should be used in this relation.



After this we end up, with our goal, of having correctly related reference data, from one table, as part of the record for another table.



Moving the relations to the table level makes correct sense. It's a change in how you've worked with AX in the past for this area, but it's a very good change. For example because of this table relations now support Dynamic Links, as well as unbound control lookups. Implementing the above, means also that when it comes time for form design, your reference field, from your Primary datasource, will enable correct lookup of data, from the reference table.

This is important to understand, for those people who are doing new custom development work, and also for those who are focused on upgrades. There is Whitepaper, for those looking to how best and tackle this for upgrades. You can find that white paper here: Migrating EDT Relations

Well I hope that on this fine Wednesday, you have a productive one, and hope that the above might come in handy, or better help your understanding of this topic, as it relates to new customization in AX 2012 as well as how this can impact and affect task when upgrading.

That's all for now, till next time!

Update: Fellow Blogging Peer Joris, over @ DAXMusings pointed a two other facts out, via twitter today for this post. First, "When you use an EDT with a reference table, it asks if you want to copy the relation onto the table where you're referencing" and Second, "[A]lso, the reference is important on EDT still for "view details" (goto main table) on dialogs." I would like to thank Joris for taking the time to add to this post, in a very positive way. These are good points that need to be understood, with the context of this post.



Visit Hillstar Business Intelligence (www.HillstarBI.com) in order to truly unlock your data trapped in your Microsoft Dynamics investment. With our value driven business intelligence strategy Hillstar help you transform into a data informed company.


"Visit the Dynamics AX Community Page today!"

AX 2012 - Security Model Design Considerations

While at AXUG Summit last week, it was clear that there are some misunderstanding surrounding the AX 2012 Security model, and it's impact on design, as well as what level of design the great new model impacts. In an article, posted by MSDW: Developers: Prepare for More Security Work When Upgrading to Microsoft Dynamics AX 2012 It is being portrayed, as if Developers and Technical Consultants will have some huge workload related to security and upgrades.

Before I continue, with at least how I think this should be understood and viewed, MSDynamicsWorld.com is a great resource, and does a great job at helping cover the Dynamics Ecosystem. Like all things however, healthy information, correction and debate is always needed.

With that said, I think the partner quoted, and the people leading the session on security that drove to this article being published do not fully understand the security model in AX 2012 and the vision for the design aspects, and what it brings. It's true there is a new security model, however it's a great step forward, and not some new burden, with no value gained.

I touched on some of this in a previous article, on the impact on design the new security model for AX 2012 will have. I tried to point out, that this is very much a Functional Design Consideration, and not some heavy extra burden on technical resources. What takes place now, is instead of security being an after thought, or something pushed to a later point in a project, it now has correct considerations through the functional design process.



The above is taking from the newly released Sure Step 2012, within the Design phase, part of the Design Activity Flow, 2.5.1 - "Create Gap Design in Functional Design Document". The owner of this process? The Application Consultant.

Now the Application Developer role, has their part to play in this, however, the design, implementation, and customer administration of security is a functional business process, not a technical one. There is technical needs to create new privileges, that tie into Security Entry points. Beyond that however, the Duties, Process Cycles, Roles, as well as assignment of Users to Roles is a business function.

The vision with the new security model, beyond the implementation or upgrade process, is meant even to be spread out among the business units, where those owners of the specific parts of the business actually control assignment of security for their respective area's.



Further more, to the upgrade, there is a new tool to help suggest upgrading groups from AX 2009, to AX 2012, which you can find on Microsoft's new InformationSource. This tool however, makes suggestions, and should not be the Application Developer Roles responsibility. This must reside on the shoulders of the Application Consultant, with the Developers help, and of course very much on the business unit owners for the customer. If correct design is not spent during the upgrade process, or implementation around this area, a great set of new functionality around security, and a better use and understanding of security for AX will be missed.

I will finish with this, we have a great new security model in AX 2012, that raises the bar, and the design concepts to the business level. This is the vision from Microsoft, to abstract out and raise out of the technical depths, so that businesses can be Dynamic and react fast based on demands. This is seen throughout design concepts from services, business workflow modeling, and more.

Hopefully with this understanding, and with the new Sure Step 2012 released, we can all be armed with the correct vision, approach, and design considerations to look at the new Security model in AX 2012 for what it is: Not a burden, but finally a correct level of consideration and design during upgrades or implementations.

That's all for now, but check back soon as a lot more to come. Till next time!

"Visit the Dynamics AX Community Page today!"

Upgrading Reports for AX 2012 - Resources

I wanted to take the time today, to point to two resources on Microsoft TechNet. This is related to upgrading reports from AX 2009, to AX 2012. The very first thing that must be clear, is that No Reports will be upgraded to the new SSRS Reporting Model for AX 2012.

With that said, MorphX reports as well as ReportLibraries can still live within AX 2012. There is actually a process in which you have to execute that will take the metadata for the AX 2009 ReportLibraries and update them, so they can live and execute within an AX 2012 instance. That resource can be found here.: Report Project Upgrade [AX 2012]

Further, there is a guide: Guidance when Upgrading Reports [AX 2012].
"Reports are not upgraded automatically during the upgrade process. Microsoft Dynamics AX provides hundreds of default, out-of-the-box reports that you can deploy and customize. To upgrade MorphX reports, we recommend that you customize a default report. The default reports run on SQL Server Reporting Services. Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality for a variety of data sources.

When upgrading to Microsoft Dynamics AX 2012, existing Reporting Services reports and reports based on the MorphX reporting framework are copied to the Microsoft Dynamics AX 2012system. However, they will not be upgraded."

The reporting model, metadata, as well as data structure changes, all within AX 2012 make it impossible really, and not a lot of value, for trying to upgrade, say an MorphX report, or even a ReportingLibrary to the new report model. This is an area of an Upgrade that will need attention for sure. Doing this, also means that you can take advantage of a lot of great new reporting tools, around Microsoft Excel PowerPivot as well as the new Microsoft Dynamics AX 2012 - Excel Add-in.

I will be covering this topic, in the class I'm leading next Tues at AXUG summit. I'm doing my final preps for sessions now, and looking forward to seeing everyone out there. You can follow me, as I will also be covering the event live from my twitter account: twitter.com/DynamicsERP.

That's all for now. Look for some updates while at AXUG, as well as my tweets. Also regular postings will pick back up after AXUG Summit next week.

Till Next Time! Cool Beans? ;-)

"Visit the Dynamics AX Community Page today!"

Microsoft Dynamics AX 2012 Upgrade Guide

This week, I did a link to Alex on DAX post, about his journey with the upgrade process of Microsoft Dynamics AX 2012. That post can be found here.: Blog Spotlight: Dynamics AX 2012 Upgrade frustrations of Alex

In that post, I pointed out that Connect should be used, for working through any issues. Now, Microsoft has recently also released the Upgrade Guide for Microsoft Dynamics AX 2012, which can be found here.: Upgrade Guide for Microsoft Dynamics AX 2012

I wanted to make sure and link to this, as soon as I saw this is public release of this guide. This will also help Alex in his path, which he recently updated his post, as he got some help already with the issues he was having.

That's all for now, but check back soon as more to come!



"Visit the Dynamics AX Community Page today!"

Blog Spotlight: Dynamics AX 2012 Upgrade frustrations of Alex

I thought I would close out Monday, with a nice spotlight on a great new blogger. His name is Alex, and he is blogging about his adventures, with upgrading an instance of Dynamics AX 2009, to Microsoft Dynamics AX 2012.

A direct link to his blog can be found here.: Alex on DAX

What caught my eye, and the blog entry in which I make mention of, above, is this one.: AoD: Dynamics AX 2012 Upgrade frustrations



What great about the posting, is its open approach of going through this process. The upgrade process, for sure has changed, and a lot of great stuff. There is also a lot of new things, and that means new headaches, specifically that Microsoft Dynamics AX 2012 is still considered in beta.

It's to be expected that you run into issues, with such a task, that has a lot of i's to dot, and t's to cross. I would expect, in the current release, to still have issues with the upgrading process, however the Beta team, and connect from Microsoft, are great resources. I would suggest Alex, if you are apart of the TAP program, or Beta program, that you use Connect, and see if there is already someone, who just might have ran into this already.

If not, I'm sure Microsoft would love to have the details of what your hitting, how to re-create it, so that it can be worked through and fixed. That's actually the best advice I can give anyone, who is needing feedback and help through processes, before AX 2012 releases to the public, in Sept.

I would like to thank Alex for taking the time, and sharing with the rest of us, and suggest he continue his writing efforts, and that you take the time to book mark his blog.

That's all for now, but this week, a new dive into Dynamics AX 2012, architect / technical style, as well as partner highlights, and more. Of course, this all leads up to the week of Sunburns & Sandals!



"Visit the Dynamics AX Community Page today!"

Microsoft Dynamics AX 2009, Roll Up (RU) 7 has been released

Microsoft has just released hotfix rollup 7 for Microsoft Dynamics AX 2009 Service Pack 1

This is a roll up of all hotfixes created since RU6, and actually contains all hotfixes since SP1 has been released. It's very important to keep up to date with RU information, as I pointed out in my article on the Value of Upgrading.

There are a good bit of kernel, application and country specific fixes that are apart of this roll up, and it's very much worth looking to see if your company can benefit from these. If your doing a new implementation, you need to make sure your partner is taking and working from the RU7.

One thing of note, the following link.: Hot Fixes Released For Microsoft Dynamics AX 2009 has not been updated yet to reflect this release.

I expect this will be updated soon, as this is the more "formal", if you will, place on PartnerSource / CustomerSource that such information is managed.

With that, you will need access to CustomerSource or PartnerSource to access RU7.

Check back soon, as more great post are coming on AX 2012, the Cloud, Decision 2011, Advanced Projects, interview with Kees Hertogh and more! Till next time!

"Visit the Dynamics AX Community Page today!"

Dr. BI Tip: SQL Server 2008 R2 & Report Builder 3 for AX 2009

As the title of this post suggest, we have Dr. BI, Michael Stashwick back for another round of tips, tricks and information around reporting with Microsoft Dynamics AX 2009 / BI.

For Michael's latest article below, he dives into SQL Server 2008 R2 and the benefits of Report Builder 3 for Ad-Hoc reporting use. This tool is great, and as he will show has great improvements over earlier versions. He also talks us through how to upgrade to Report Builder 3 with SQL Server 2008 R2.

---



I can’t think of any single subject clients ask me about more than self-service Business Intelligence (BI) and ad hoc reporting. There seems to be no ceiling to the demand that has increased daily for the past few years, and it’s mostly due to the very robust BI stacks available.

Unfortunately, the primary ad hoc tool that comes packaged with Dynamics AX, Report Builder 1.0, is a bit archaic and leaves users underwhelmed. Fortunately, the latest version, 3.0, is rich with functionality and pleases every super user that I’ve introduced it to.

Implementing Report Builder 3.0 requires SQL Server 2008 R2, and the upgrade path, which I’m going to discuss in this article, should be anything but intimidating.

To begin, there is a free downloadable Upgrade Advisor that removes all compatibility guesswork. After running the Analysis Wizard against all installed SQL Server components, the Upgrade Advisor Report Viewer will provide a list of all issues with links to MSDN for assistance. Even in the most perfect situation, there will always be one issue--the custom extensions and assemblies from the AX installation.



This is nothing to worry about and should be expected. Once all else checks out, run the R2 upgrade executable. After a successful upgrade, the first logical verification step is to run Report Manager and a deployed report.

Immediately accessing Report Manager will result in a cryptic error message that you’ve probably never seen before:

"The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version."

After giving the computer a verbal snarky response, gather more meaningful information by logging into Report Server. You will get an error message that the ‘Microsoft.Dynamics.Framework.ReportsExtensions’ could not be loaded. This is exactly what the Upgrade Advisor warned of in the beginning of the procedure.



The reason this happens is that in the upgrade process, a new sub-folder is made, as opposed to files being appended, in your Microsoft SQL Server directory. The necessary information to run AX Reporting Extensions can’t be located due to this move.

The simplest fix is to re-install Reporting Extensions from your AX install media. Of course, it must first be uninstalled before it can be re-installed.

There is one last step in upgrade process. If you tried to run a report now, it would fail as the system would be “unable to find the file specified.”



Because of this, all reports must be deleted and re-deployed to the Report Server. This realization made me so happy to have Report Libraries in AX 2009, because the countless number of reports, including any custom AX 2009 SRS reports, can be deployed in a single action.

Now, Report Builder 3.0 will launch by default when accessed by Report Manager. The additional functionality provided (compared to 1.0) is staggering, and can be seen in the MSDN article, Comparing Report Authoring Environments. Not every piece of functionality may be relevant to AX, but the UI is grossly improved with the familiar ribbon interface, and more in-depth querying is available.


---

I would like to thank 'Dr. BI' for taking the time and sharing with us yet another reason why Microsoft Dynamics AX is so powerful.: It's Continued use of the rest of the Microsoft Stack

Also, this ties right into the use of tools like Globe Software Atlas, and Microsoft PowerPivot (Microsoft Dynamics AX 2012 and the importance of PowerPivot) for Ad-Hoc and Self-Service BI needs.

That's all for now, till next time!

"Visit the Dynamics AX Community Page today!"

Guest Column: The Value of Upgrading

Well today, I finally am feeling somewhat better, and took the time to write a new guest column on the Microsoft Dynamics Community, offical site. A direct link to that new column entry can be found here.: The Value of Upgrading

I hope that I captured the importance and reason a company would care about their Dynamics investment, and hope that this gets companies thinking about making sure they are asking and planning to helkp stay current and get the most out of their AX investment.

This comes in the same week, that Dynamics AX Rollup 6 has been released! Dynamics AX 2009 Rollup 6 has been released to Partner Source and Customer Source

That's all for this week, and next week is a short turkey week! I will be posting next week as that great Turkey day approaches! Till next time!

"Visit the Dynamics AX Community Page today!"