Microsoft Dynamics 365 Blog

Published
15 min read

Return material adjustment (RMA) processing through the mobile device 

This blog post assumes a working knowledge of the newWarehouse management module released in Microsoft Dynamics AX 2012 R3.   The process of receiving a Return material adjust (RMA)using the new WMS mobile device functionality is very similar to processing aninbound transaction such as a purchase order. The following steps are intendedas a walkthrough of

Published
4 min read

Coffee Break – keeping stuff in the cloud 

In the last few Coffee Break posts we have been looking at virtual hard disks (VHDs) and virtual machines (VMs). Now let’s combine the two in the cloud. Coffee Break 11 – Provisioning – Using Microsoft Azure storage to keep VHDs and other useful stuff in the cloud Provisioning a new instance of Microsoft Dynamics NAV is like

Published
1 min read

Microsoft Dynamics AX 2012 Upgrade – Using the State Transfer Tool with AX 2009, you can potentially have duplicate records created within table Shadow_DirPartyRelationship 

  This specific issue occurs only when using the state transfer tool in AX 2009. The problem is as follows: We create new records in the Shadow_DirPartyRelationship. The unique index on this references RefRecId. The RefRecId will become the RecId for DirPartyRelationship during the bulk copy in AX 2012. We use the SystemSequences NextVal from

Published
1 min read

Dynamics AX R3 Demo Image: “The price cannot be calculated for the item. Please manually enter the correct price” error in EPOS 

Update (2015-08-13):  If you are using the 2013 R3 CU9 demo image you may run into the same error with a (much) different root cause and workaround.  Please see this post for notes on how to fix that issue. If you are using the Dynamics AX demo image (https://technet.microsoft.com/en-us/library/dn741578.aspx) you may have seen this error

Published
<1 min read

Moving AXModelstore from Source environment to Target environment with different DB collation 

AX 2012 R2/R3 We have in support received some queries for recommendations moving the AXModelStore from a Model database to another Model database with different collation. Conclusion:  The AXModelStore file we create is specific to SQL_Latin collations, saying that, for metadata, AX only supports the SQL_Latin… collation on string fields, and that is why even Model