Dynamics AX Sustained Engineering

Performance issue in "Open Transaction Edit" form

2009-10-26T16:00:00Z

SE has noticed a performance issue in “Open Transaction Edit” form (AP >> Vendor Details form >> "Open Transaction Editing") in AX 2009 SP1. Post our investigations, we see that much time is consumed sizing the grid columns. Implementing a customization on the VendOpenTrans form will significantly reduce the time needed to open the form. ON test results from our end , we saw an improvement from 60 seconds to 11 seconds post implementing this customization .

Please note that you can also utilize the customization on various other forms that pose the same impact in performance reasons. Below are details on how to work around this issue by making changes to the \forms\VendOpenTrans with some code snippets given below.

Pre requisite : Ensure to have KB 968397 installed on both the client & server. This KB is also included Ax 2009 SP1 Roll-up 2 and is available here

Code snippets :

\Forms\VendOpenTrans\Designs\Design\[Tab:TabControl]\[TabPage:OverviewTab]\[Grid:OverviewGrid]

Change the AutoDeclaration Property from No to Yes.

The code snippet below contains an addition of “overviewGrid.autoSizeColumns(false)” which was a kernel method that was introduced by the referenced KB 968397 fix.

\Forms\VendOpenTrans\Designs\Design\[Tab:TabControl]\[TabPage:OverviewTab]\[Grid:OverviewGrid]

…

super();

overviewGrid.autoSizeColumns (false); //added line

switch (originator.TableId)

…

The Company info table is updated:

A new field is added called DataArea which uses extended data type “CompanyID”

Method initValue() has 1 line added to populate the new field when a new company record is created.

void initValue()

{

super();

this.dataArea = this.dataAreaId; //line added

this.LanguageId = new Session().interfaceLanguage();

}

Secondly the entire CustVendOpenTransBalances.initCustVendBalanceMst() method is re-written as follows:

/// <summary>

/// Initializes the posted customer or vendor balance in the monetary standard (MST) currency.

/// </summary>

/// <param name="_custVendAccount">

/// The customer or vendor account number that is used to initialize the balance.

/// </param>

/// <param name="_isCustomerAccount">

/// A Boolean value that indicates whether to initialize the posted customer balance or the vendor

/// balance.

/// </param>

protected void initCustVendBalanceMst(AccountNum _custVendAccount, boolean _isCustomerAccount)

{

DirPartyId custVendPartyId;

CustVendTrans custVendTrans;

CustTrans custTrans;

VendTrans vendTrans;

CustVendTable custVendTable;

CustTable custTable;

VendTable vendTable;

CurrencyCode transMstCurrency;

Amount transMstBalance;

CurrencyExchHelper currencyExchHelper;

CompanyInfo companyInfo;

changecompany(custVendCompany)

{

if (_isCustomerAccount)

{

custTable = CustTable::find(_custVendAccount);

custVendPartyId = custTable.PartyId;

custVendTrans = custTrans;

custVendTable = custTable;

}

else

{

vendTable = VendTable::find(_custVendAccount);

custVendPartyId = vendTable.PartyId;

custVendTrans = vendTrans;

custVendTable = vendTable;

}

// Initialize currency exchange helper

currencyExchHelper = CurrencyExchHelper::construct();

currencyExchHelper.parmCompany(displayCompany);

while select crossCompany:sharedServiceCompanies sum(AmountMst), CurrencyCode, AccountNum from custVendTrans

order by companyInfo.CurrencyCode asc

group by companyInfo.CurrencyCode

join DataArea, CurrencyCode from companyInfo

where companyInfo.DataArea == custVendTrans.dataAreaId

exists join AccountNum, PartyId from custVendTable

where custVendTable.AccountNum == custVendTrans.AccountNum

&& custVendTable.PartyId == custVendPartyId

{

transMstCurrency = companyInfo.CurrencyCode;

transMstBalance = custVendTrans.AmountMST;

// Convert to the company currency of the display company using the system date and the display company exchange rate, if necessary

if (transMstCurrency != displayMstCurrency)

{

if (Currency::existByCompany(displayCompany, transMstCurrency))

{

// Calculate the balance from the transaction company if its currency exists in the display company.

currencyExchHelper.parmCurrency(transMstCurrency);

transMstBalance = currencyExchHelper.calculateAmountCurToMst(transMstBalance, true);

}

else

{

// Otherwise the balance from that company should not be added to the total.

transMstBalance = 0;

}

custVendBalanceMst += transMstBalance;

}

New Compatibility Testing Results - October 2009

2009-10-12T13:31:00Z

Dynamics AX Sustained Engineering Team has completed the following compatibility tests for the new releases of the following external stack components :

Microsoft Product	Dynamics AX version
Windows 7	Dynamics AX 4.0 SP2 and Dynamics AX 2009 RTM and SP1 Supported as a client only, in 32 bit and 64 bit mode
Windows Server 2008 R2	Dynamics AX 4.0 SP2 and Dynamics AX 2009 RTM and SP1 Operating System Supported in 64 bit only Note: for upgrade from Windows Server 2008 to R2 with SharePoint 2007 already installed please refer to KB962935 and the following Technet article.
Windows Server 2008 Service Pack 2	Dynamics AX 4.0 SP2 and Dynamics AX 2009 RTM and SP1 Operating System Supported in 32 bit and 64 bit mode
Windows Terminal Services	Dynamics AX 4.0 SP2 and Dynamics AX 2009 RTM and SP1
Office 2007 Service Pack 2	Dynamics AX 4.0 SP2 and Dynamics AX 2009 RTM and SP1

Please watch this space for compatibility & support updates. For further information, feel free to contact daxsecom@microsoft.com

Dynamics AX 2009 Rollup 3 has been released to Partner Source and Customer Source

2009-10-01T01:33:00Z

Recently, we had given a hint on RU-3 that was planned for a September release. Last week, we released the rollup to Partner Source and Customer Source. This rollup carries the richest content compared to the previous ones in terms of the number of the country specific features. Additionally, RU-3 for Microsoft Dynamics AX 2009 SP1 includes Hebrew language support (User interface only) for Microsoft Dynamics AX 2009 SP1, providing the language baseline for the GLS-IL (Israel) layer that is planned to be released later this year.

Due to cumulative nature of the rollups, RU-3 carries all of the content that has been released in RU-1 and RU-2.

Here are the links to the KB articles for RU-3:

· Dynamics AX 2009 RTM RU-3 KB Article à KB974407 (Download Package Size ~ 60MB)

· Dynamics AX 2009 SP1 RU-3 KB Article à KB974409 (Download Package Size ~ 100MB)

Microsoft Dynamics AX 4.0 and AX 2009 are compatible with Microsoft Windows 7 and Microsoft Windows Server 2008 R2

2009-09-17T18:19:00Z

Dynamics AX Sustained Engineering is proud to announce the following compatibility between the released versions of Dynamics AX and the Release Candidate of Windows 7 and Windows Server 2008 R2:

Microsoft Product	Dynamics AX version
Windows 7	Dynamics AX 4.0 SP2 and Dynamics AX 2009 RTM and SP1 Supported as a client only, in 32 bits and 64 bits mode.
Windows Server 2008 R2	Dynamics AX 4.0 SP2 and Dynamics AX 2009 RTM and SP1 Operating System Supported in 64 bits only.

The System Requirements of Dynamics AX 4 and Dynamics AX 2009 will be updated on Customer Source and Partner Source and can be found at the links below.

   CustomerSource AX 4.0: https://mbs.microsoft.com/customersource/documentation/systemrequirements/systemrequirementsax40.htm
   PartnerSource AX 4.0: https://mbs.microsoft.com/partnersource/documentation/systemrequirements/systemrequirementsax40.htm
   CustomerSource AX 2009: https://mbs.microsoft.com/customersource/documentation/systemrequirements/ax2009systemrequirements.htm
   PartnerSource AX 2009: https://mbs.microsoft.com/partnersource/documentation/systemrequirements/ax2009systemrequirements.htm

For further information, feel free to contact daxsecom@microsoft.com

Thanks,

Dynamics AX Sustained Engineering

Microsoft Dynamics AX Roll-up 3 is under development...

2009-09-01T01:21:00Z

As you know, the SE team had started releasing hotfix roll-ups for Microsoft Dynamics AX 2009 RTM and SP1 platforms back in March 2009. As mentioned in the previous blog post, the goal for the roll-ups has been to provide an easy way of deploying Microsoft Dynamics AX with the latest hotfixes and country specific updates on a given Service Pack level. Since so far, we have received very positive feedback from partners on the availability of hotfixes and country-specific updates in the form of a roll-up package.

Following Roll-up 1 in March and Roll-up 2 in June, Roll-up 3 for AX2009 RTM and SP1 is currently under development and scheduled to be released to Partner Source and Customer Source in the second half of September. In addition to the hotfixes, Roll-up 3 is going to carry multiple country-specific updates for various regions on SYP and GLS layers except for GLS-TR.

We will post a separate announcement with links to the release KB articles at the time of the RTW. Stay tuned!

Microsoft Dynamics AX 2009 Roll-up 2 is available on Partner Source and Customer Source!

2009-07-10T05:07:00Z

To assist our partners and customers in their new Microsoft Dynamics AX deployments, the SE team started releasing roll-ups for Microsoft Dynamics AX 2009 RTM and SP1 platforms. The roll-ups aim to provide an easy way of deploying Microsoft Dynamics AX with the latest hotfixes on a given Service Pack level. Roll-up 2 for AX2009 RTM and SP1 has been available on Partner Source and Customer Source as of June 29^th, 2009. Please find the roll-up KB articles below:

Roll-up	KB Number	Package Size
Dynamics AX 2009 RTM RU-2 KB Article	KB971535	~60MB
Dynamics AX 2009 SP1 RU-2 KB Article	KB971536	~80MB

There will be one roll-up package for each Service Pack level. Each roll-up will carry all previously released hotfixes up to one month prior to the release of the roll-up and country specific updates. Each roll-up will be cumulative and will not require the presence of the previous roll-up on the system.

The roll-up package will contain both a cumulative kernel update and a cumulative application update. Although there is no dependency between these two updates, we recommend that you install both of the updates together. The roll-up will be installed on P-layers (i.e. SYP and GLP) and update the SYS layer as well as the GLS layer that is installed on the system.

Updated Lifecycle policy for Microsoft Dynamics Products

2009-07-07T00:23:00Z

Microsoft Dynamics Products have announced a new lifecycle policy - shifting from a 12 month model to a 24 month model. More information can be found at the Help and Support page listed below:

http://support.microsoft.com/gp/lifean41

Upgrade script ReleaseUpdateDB41_Invent\updateInventItemPrice () fails without LogisticsAdvanced license code

2009-07-06T23:58:00Z

During upgrade from Axapta 3.0 to Dynamics AX 4.0 or AX 2009, upgrade script ReleaseUpdateDB41_Invent\updateInventItemPrice () fails in the absence of LogisticsAdvanced license code. License codes are used to enable configuration keys. Absence of LogisticsAdvanced license codes cause the disabling of the LogisticsAdvanced configuration key, which, in turn, removes the InventDimCombination Table from the database. This results in the upgrade script ReleaseUpdateDB41_Invent\updateInventItemPrice () failing.

The fix is to add a configuration key validation before processing table InventDimCombination, in \Classes\ReleaseUpdateDB41_Invent\updateInventItemPrice ()

public void updateInventItemPrice()

{

CostingVersion costingVersion;

...

// copy sales prices

insertInventItemPrice(#commonCostingVersionId, ModuleInventPurchSales::Sales, CostingVersionPriceType::Sales, NoYes::No, NoYes::No, NoYes::No, NoYes::No,

InventItemCostingType::Undefined);

if(new DictConfigurationKey(new DictTable(tablenum(InventDimCombination)).configurationKeyId()).enabled())

{

// copy records from InventDimCombination to InventItemPrice

// copy cost prices

insertInventItemPriceDimCost(#commonCostingVersionId, NoYes::No, InventItemCostingType::Undefined);

insertInventItemPriceDimCost('', NoYes::Yes, InventItemCostingType::Last);

// copy purcahse prices

insertInventItemPriceDimSalesPurchase(#commonCostingVersionId, ModuleInventPurchSales::Purch, CostingVersionPriceType::Purch, NoYes::No, NoYes::Yes,

InventItemCostingType::Undefined);

insertInventItemPriceDimSalesPurchase('', ModuleInventPurchSales::Purch, CostingVersionPriceType::Purch, NoYes::Yes, NoYes::Yes,

InventItemCostingType::Last);

// copy sales prices

insertInventItemPriceDimSalesPurchase(#commonCostingVersionId, ModuleInventPurchSales::Sales, CostingVersionPriceType::Sales, NoYes::No, NoYes::No,

InventItemCostingType::Undefined);

}

if (rowCount)

...

ttscommit;

}

New Compatibility Testing Results

2009-06-04T23:54:00Z

Dynamics AX Sustained Engineering Team has completed the following compatibility tests for the new releases of the following external stack components :

Microsoft Product	Dynamics AX version
Microsoft Internet Explorer 8.0 version 8.0.6001.17184	With Dynamics AX 4.0 SP2 and Dynamics AX 2009
Microsoft SQL Server 2008 Service Pack 1 version CTP 10.00.2520.00	With Dynamics AX 4.0 SP2 and Dynamics AX 2009
	Note: Report Builder 2.0 capabilities was not tested
Microsoft BizTalk Server 2009	With Dynamics AX 4.0 SP2 and Dynamics AX 2009
	Including the RFID connectivity
	Note: The “side by side” scenario with Dynamics AX 4.0 and Dynamics AX 2009 on the same box is not supported.

We are currently in process of completion in testing the following :

Windows Server 2008 SP2

Windows Essential Business Server

Please watch this space for compatibility & support updates. For further information, feel free to contact daxsecom@microsoft.com

Thanks,

Dynamics AX Sustained Engineering

Microsoft Dynamics AX 2009 Roll-up 1 is available on Partner Source and Customer Source!

2009-04-14T22:04:00Z

To assist our partners and customers in their new Microsoft Dynamics AX deployments, the SE team started releasing roll-ups for Microsoft Dynamics AX 2009 RTM and SP1 platforms. The roll-ups aim to provide an easy way of deploying Microsoft Dynamics AX with the latest hotfixes on a given Service Pack level. The first roll-up packages for AX2009 RTM and SP1 have been available on Partner Source and Customer Source since mid-March and we have been seeing hundreds of downloads. Please find the roll-up KB articles below:

Roll-up	KB Number	Package Size
Dynamics AX 2009 RTM RU-1 KB Article	KB967146	~60MB
Dynamics AX 2009 SP1 RU-1 KB Article	KB967145	~75MB

There will be one roll-up package for each Service Pack level. Each roll-up will carry all previously released hotfixes and updates up to one month prior to the release of the roll-up. Each roll-up will be cumulative and will not require the presence of the previous roll-up on the system. The roll-ups will also carry the tax updates that have been released previously.

Moving forward, the roll-ups will be announced at least one month prior to the release date. Currently, SE team is working on the plans for roll-up 2.

SQL Server 2005 sp3 & SQL Server 2008 with Dynamics AX

2009-02-11T22:07:00Z

Microsoft SQL Server 2005 Service Pack 3 is now compatible with Dynamics AX 4.0 SP2 and Dynamics AX 2009 SP1. The Dynamics AX SE team would also like to announce the availability of the latest SQL Server 2008 support packages for Dynamics AX 2009. This update now includes a fix for a variant of the “Deploy ODC Files” issue which was not addressed in the previous support pack release (KB957312-v2). This variant also affects Dynamics AX 2009 SP1 and a SP1 specific hot fix is also available.

Issue summary:

The issue is that the business connector calls into Microsoft.Dynamics.AnalysisServices during web initialization prior to the custom resolve handler fix that was implemented with the fix for KB957312-v2. The issue is similar in that it attempts to load the SSAS 2005 library but is not found. This surfaces later as a failure when attempting to deploy the ODC file even though the custom resolve handler is loaded … because the previous resolution failure is cached. The fix which is to load the custom resolve handler prior to loading the business connector within the EP framework assembly is now available in KB957312-v3 (RTM hot fix) and KB960158 (SP1 hot fix).

Package availability:

AX2009 RTM SQL Support Pack (v3) [KB957312]: https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;957312

AX2009 SP1 Hot fix [KB960158]: https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;960158 ( KB coming soon..at the same link )

For DAX 4.0 SP2, please note the following:

Database	Notes
Microsoft SQL Server 2008	Supported with Microsoft Dynamics AX 4.0 Service Pack 2 with kernel version 4.0.2503.358 or higher. To obtain this version, you must download the hot fix described in Knowledge Base article number 944115.

For more details on this see here. Also for more information on SQL Server Reporting Services and SQL Server Analysis Services integration with AX 2009 read up here.

For further information, feel free to contact daxsecom@microsoft.com

Thanks,

Dynamics AX Sustained Engineering

Compatibility Testing

2009-02-10T07:06:00Z

Dynamics AX Sustained Engineering executes Quarterly External Dependency Tests to provide information to customers and partners on the existing products releases. In this blog you shall get to hear the latest compatibility matrix on AX 3 SP6, AX 4.0 SP1 and SP2 , AX 2009 RTM and AX 2009 SP1. Check this space often to keep yourself up to date on our latest compatibility tests.

For more specific information contact daxsecom@microsoft.com

Thanks,

DAX Sustained Engineering

Microsoft Dynamics AX 2009 Service Pack 1 Released

2008-11-19T07:03:00Z

Microsoft Dynamics® AX 2009 Service Pack 1 has been released!

We are pleased to announce the general availability (GA) of Microsoft Dynamics® AX2009 Service Pack 1 (SP1)! The release announcement was done today (November 18^th, 2008) at the Convergence 2008 Conference in Copenhagen, Denmark. Currently, the Service Pack is available to download on PartnerSource and CustomerSource.

What’s in Service Pack 1?

SP1 contains the complete set of updates that Microsoft has issued since the June 2008 RTM release of Microsoft Dynamics AX 2009, as well as a number of enhancements and new features to improve the product’s functionality and user experience. The majority of these fixes are specific to individual modules or workflows, and as such should not require a full re-evaluation cycle of Dynamics AX 2009 SP1 at sites where the RTM version of the product is already under evaluation. Our goal with SP1 was to put out a low cost service pack to deploy and we believe that we achieved this goal by only accepting changes required to support future targeted releases that will require SP1.

Some of the enhancements carried in SP1 are Electronic Signature, Right-to-Left Date Support and Time Zone Patching Tool. For the full list of enhancements in SP1, take a look at the What’s New Document available on PartnerSource and CustomerSource. The document is updated with a section explaining these enhancements.

Beginning with SP1, Microsoft Dynamics AX 2009 also provides support for Microsoft SQL Server® 2008. Additionally, the SP1 installer updates both the SYS and GLS layers of the product. This means, for example, that if you already have GLS-TR installed on your system, SP1 will update this layer during the installation process.

Along with Service Pack 1, we also released Microsoft Dynamics® AX 2009 Client Help Update, which carries the updated help content for Microsoft Dynamics® AX 2009 and new help topics for the enhancements and features introduced by SP1. We decided to make this package available as a separate download due to the size of its content. Please check out the Installing Service Pack 1 for Microsoft Dynamics AX 2009 document for the details of installing the contents of the help update on your system.

One additional data point about SP1 is that it requires to be existent on the system. In other words, SP1 does not include Microsoft Dynamics® AX 2009 RTM, but rather is an update that installs on top of Microsoft Dynamics® AX 2009 RTM.

SP1 is high quality and low cost to deploy! During our pre-release customer program, we have received very positive feedback on SP1, which makes us we believe that our partners and customers will like what SP1 offers to their business and environment. Enjoy the ride!

Dynamics AX 2009 Patching

2008-10-03T17:20:00Z

A question that many customers and partners have regarding AX 2009 is how patching is handled for the product. Changes have been made in Dynamics AX 2009 to address some of the concerns that existed with the patching strategy that was in place for Dynamics AX 4.0.

A quick summary of how patching is done in Dynamics AX 4.0:

SYS Layer code patched via a layer file for the DIS layer
GLS Layer code patched via an .xpo file

There are some positives and negatives to this patching approach which I have summarized here:

Positives:

Cumulative layer (DIS) was tested with all fixes included so all fixes work together
Application version incremented with each patch allowing users to know exactly what patches were installed

Negatives:

Fixes were shipped in a cumulative layer - Difficult to get a single fix out of the layer
Larger scope of customization analysis due to the cumulative layer - similar to a Service Pack
Lack of detailed fix documentation
Over-layering of region-specific code (GLS) due to SYS patches living in the DIS layer
Inconsistent patching experience for SYS and GLS code

This feedback was used to make some crucial changes in the design of Dynamics AX 2009 to allow for a more convenient and usable patching approach. For Dynamics AX 2009 individual patches are available for SYS and GLS code. The key change to delivering the individual fix is that Dynamics AX will now allow the import of a signed .xpo file to a particular layer. For a patch to code that resides in the SYS layer a patch would be made that would load an .xpo into the SYP layer. GLS code patches will be made to the GLP layer. This is helpful for multiple reasons. First, the SYP layer is controlled by Microsoft and does not allow others to include code in the layer. This means that only patches released from Microsoft will reside in the layer. At the time of a service pack update, we can also move the axsyp.aod automatically to the old folder for comparison purposes as we know where previously installed patches will reside on the system. The second advantage to patching SYS code in the SYP layer is that any over-layering issues can be avoided. By patching in the proper layer a patch will not overwrite any country-specific functionality that would have expanded on the global code base.

For an application hot fix we ship a package that contains the following:

Licenseterms folder
Support folder
axpatch.exe
kbXXXXXX.txt
kbXXXXXX-[layer].cab

A patch is installed for Dynamics AX 2009 by clicking on axpatch.exe and following the prompts from the installer. The *.cab file contains the Microsoft signed .xpo as well as an .xml file which directs the installer to the appropriate layer to patch.

The folder named licenseterms contains the license terms used in the installer for each of the supported languages. In the support folder the 24 languages for the patch installer are included as well as necessary files for managing the import of a patch.

The kbXXXXXX.txt file contains the affected objects including methods. This is helpful in initial analysis to determine if the affected object has been modified on your system in any other layer. After the initial analysis the patch can be applied to a test system and the compare tool inside of Dynamics AX can be used to analyze any changes that need to be made to merge the patch into the environment before being deployed on the live system.

Additionally, once an application patch has been applied a new class can be found in the Application Object Tree (AOT) called SysHotFixManifest. This class will contain a method with the KB Article number representing each patch applied to the system. This is done to allow the tracking of patches deployed in AX 2009 as the application version cannot be incremented when using individual patches.

In summary, Dynamics AX 2009 can be patched via a Microsoft signed .xpo file in a specific layer. This enables better tracing of installed patches as well as isolating Microsoft code from customizations and third party applications. The patches installed on an environment can be seen in the SysHotFixManifest class and will appear as methods indicating each KB Article applied.

For additional information on patching Dynamics AX 2009 please see the Dynamics AX 2009 Patching Whitepaper which has been published on PartnerSource\CustomerSource.

PartnerSource

https://mbs.microsoft.com/partnersource/deployment/documentation/whitepapers/AX2009Patching

CustomerSource

https://mbs.microsoft.com/customersource/support/documentation/whitepapers/AX2009Patching

Please feel free to comment with your feedback or any questions regarding this approach.

Thanks for reading and have a great day!

Dynamics AX Sustained Engineering Team

Welcome!

2008-10-03T17:18:00Z

Thanks for finding our blog!

Welcome to the Dynamics AX Sustained Engineering Team’s blog. Our goal is to use this blog to interact with customers regarding patching and servicing of released product. The posts to this blog are intended to address and discuss issues pertaining to Dynamics AX Servicing with customers and partners who work with Dynamics AX. We plan to share information regarding the methods in which the Dynamics AX product is serviced as well as helpful hints or recommendations for some common issues we see. We will post periodically regarding different topics\challenges people are facing and hope to have some good discussion regarding these items. Our goal is to post topics on at least a monthly basis but you may find that posts may occur more or less frequently based on our availability. Please check back periodically to see what the latest posts\comments are and hopefully find answers to some of the questions you may have.

Thanks,

Dynamics AX Sustained Engineering

Dynamics AX Sustained Engineering

Performance issue in "Open Transaction Edit" form

New Compatibility Testing Results - October 2009

Dynamics AX Sustained Engineering Team has completed the following compatibility tests for the new releases of the following external stack components :

Dynamics AX 2009 Rollup 3 has been released to Partner Source and Customer Source

Microsoft Dynamics AX 4.0 and AX 2009 are compatible with Microsoft Windows 7 and Microsoft Windows Server 2008 R2

Microsoft Dynamics AX Roll-up 3 is under development...

Microsoft Dynamics AX 2009 Roll-up 2 is available on Partner Source and Customer Source!

Updated Lifecycle policy for Microsoft Dynamics Products

Upgrade script ReleaseUpdateDB41_Invent\updateInventItemPrice () fails without LogisticsAdvanced license code

New Compatibility Testing Results

Microsoft Dynamics AX 2009 Roll-up 1 is available on Partner Source and Customer Source!

SQL Server 2005 sp3 &amp; SQL Server 2008 with Dynamics AX

Compatibility Testing

Microsoft Dynamics AX 2009 Service Pack 1 Released

Dynamics AX 2009 Patching

Welcome!

SQL Server 2005 sp3 & SQL Server 2008 with Dynamics AX