Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012
CRM Connector in Microsoft Dynamics AX 2012
Financials Management in Microsoft Dynamics AX 2012
Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
This page provides you with a consolidated list of published documentation, sources of information, known issues, solutions and tips and tricks for troubleshooting the Microsoft Dynamics AX 2012 Feature Pack and Microsoft Dynamics AX 2012 R2.
On this page:
View and download demo packages, training guides and popular documents for Microsoft Dynamics AX 2012, and Microsoft Dynamics AX 2012 R2.
There are several known issues in the Retail applications area of Microsoft Dynamics AX 2012, Microsoft Dynamics AX 2012 Feature pack and Microsoft Dynamics AX 2012 R2 for which we have released a variety of different relevant hotfixes. It is highly recommended that you are on the most recent updates for Microsoft Dynamics AX 2012 Feature Pack or Microsoft Dynamics AX 2012 R2.
Below are the links to the list of relevant hotfixes for each release.
N jobs N jobs push out all data from a table to the POS every time the N job runs. It clears the POS tables and replaces it with a fresh copy of AX data. The A jobs are more lightweight and only push changes, sending less data. Only new or updated records are sent to the POS when these run. For example A jobs are required if you want to send information to POS1 and not to POS2. In this scenario, if an N job were used instead, then both POS1 and POS2 would get all of the data. A jobs can also be used to send different sets of data to different stores.
By default, Commerce data exchange: Synch service is set to use IPSec to secure its communications for PCI compliance. If you want to use this, you must set up your network to support IPSec as well. You can disable IPSec in the Commerce data exchange: Synch service settings, but doing so would then require another form of communication security to be implemented to meet the PCI compliance requirements.
A-Jobs use a timestamp as a marker to indicate the last time that the distribution schedule was run. The next time that this distribution schedule is run, only actions with a timestamp later than that marker will be processed
To update the data for the store that was offline at the time that the A-Jobs were run, go to the distribution schedule that failed, select the A-Job that failed and then click Scheduler log. Select the occurrence that failed and click Rerun scheduler job. Then select the store where you want to send the data.
Still having trouble...
If you are experiencing issues downloading the install file or documentation on CustomerSource/PartnerSource, please contact ITMBSSUP@microsoft.com
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13