Menu

Microsoft Dynamics AX/365 Services FAQ

Feel free to browse our pages for information about our services and Dynamics AX. If you still have questions, you may contact us in the form below and our team will get back to as soon as possible.

Yes, with this release Microsoft® included a new module called the “Data export / import framework”. This new module comes with over 90 predefined templates from GL balances to customers and sales orders etc. The framework uses an intuitive user interface that allows users with no knowledge of the table structure and relations to import and update data from excel spreadsheets or other formats.

We recommend reviewing the following to ensure Microsoft Dynamics AX is running optimally:

  • Review Microsoft Dynamics AX generally accepted best practices for Microsoft® SQL Server, including committed snapshot isolation, max degree of parallelism, temp size and placement, memory, log and data file settings. Incorrect settings can have a significant impact on performance. Review OS settings, including OS power management and ensure it is set to high performance.
  • Review SQL version, trace flags and hotfixes. Hotfixes for older versions of Microsoft SQL server can improve performance. Trace flags can be switched on to activate these fixes, including trace flags 4199 and 4136.
  • Review SQL maintenance. Review indexing, statistics updates, backup policies and auto growth settings and alerts. Configure alert to monitor scenarios that may affect performance, such as database auto growth.
  • Review customizations in Microsoft Dynamics AX. Run the Microsoft Dynamics AX developer best practice check to look for tables with missing indexes. Review code and customizations to ensure that they meet generally accepted Microsoft Dynamics AX development best practices. This can surface poorly written customizations that are not optimal and introduce performance issues, for example large tables with no or incorrect indexes.
  • Configure client tracing in Microsoft Dynamics AX. It is possible to monitor specific users’ performance, which is significant as this allows us to link a performance issue (for example a long running query) to a specific line of code in Microsoft Dynamics AX, and therefore allow us to identify and fix the code or process that is causing the performance issue.
  • Review Microsoft Dynamics AX configurations, setups, parameters and batch jobs that may affect performance. For example, configuring a lot of continuous number sequences without pre-allocation may affect performance. Review database log configuration (especially important if you run MRP and BOM calculations), and ensure excessive database logging is not affecting performance.
  • Review Microsoft Dynamics AX hotfixes and patches regularly to look for any fixes that might improve performance.

There are two main factors that can drive the scope of an upgrade. The first one is the upgrade type. Is the upgrade strictly a technical upgrade, meaning that the application, customizations and data will be upgraded using the Microsoft® upgrade scripts, or will the upgrade involve a re-implementation, meaning that the system will be set up from scratch using a new installation?

The second major driver is the amount of customized code. If the application is very heavily customized, a technical upgrade may not be suitable. Of course, there are many other factors, but generally speaking, a technical upgrade with a moderate custom code will require 2 and 3 months whereas the re-implementation approach can take 9 and 12 months or more.

Any new implementations of Microsoft Dynamics® AX 2012 R2 would include at least service pack (cumulative update) 7, which was released in February 2014. Microsoft Dynamics AX 2012 R3 was released May 1, 2014. Therefore, the actual time on market between versions is less than three months. In addition, R3 should be considered an evolution of a mature product rather than a revolutionary release from Microsoft®.

This is evident in the similar kernels and technical architecture the two-version share. AX 2012 R2 also supports SQL Server 2014, which helps future-proof your installation. Avantiico can provide a full list of R3 vs. R2 advantages, which can quickly help your organization feel confident in your upgrade version choice.

Avantiico is a Microsoft Value Added Reseller (VAR) and supports organizations in North America and Europe with all matters regarding Microsoft licensing. Avantiico resells Dynamics AX using the Business Value Licensing (BVL) Price List.

Yes, Microsoft® requires that all customers be associated with a Certified Microsoft Partner at all times, even if you engage with Microsoft Consulting or Premier Support. The “Partner of Record” is your entry point to Microsoft and should provide you with advice relevant to your Microsoft solutions. Your Partner of Record is responsible for renewing your Business Ready Enhancement or Software Assurance Plan. The Microsoft Change of Reseller form must be used to designate a new partner.