r3

Azure Service Bus Messaging with Dynamics AX 2012 (part 1)


As Dynamics AX becomes more prominent in your overall IT landscape, integration scenarios will become more challenging.  We all know the joys of scheduled maintenance in terms of AX, as it is best practice to take your production system offline and deploy updates in the form of modelstores. 

While a good reboot is often a healthy thing, we like to prevent the “We’re down for maintenance, come back soon!” messages on any of our customer-facing software like a website, mobile, and supply chain applications to name a few.

SSRS Reports Won't Email as Attachment in Batch


During our AX 2012 upgrade from RTM to R3, we found that we could no longer have reports run in Batch that print via email with an attachment.  This worked perfect in RTM, but R3 seems to have introduced some new .NET based classes that behave differently.  I'll show you a work around we have found, while we await a response from Microsoft.

AXR3 - SysOperation AIF Patch


A quick fix

In reviewing the AIF Service generation classes between RTM CU5 + Feature Pack and R3, I found a small difference in the AifServiceDataTypeGenerator class.

Specifically the method highlighted in the image above, the generateDataContractClass.  Previously, we had been able to deploy AIF ports that used Data Contract Classes which extend SysOperationDataContractBase. In AX 2012 R3, this was broken - for details see my previous post.

AX 2012 R3 Upgrade Gotchas


In our upgrade to AX 2012 R3 from AX 2012 RTM ( or R1 ), we've run in to some interesting scenarios.  Be it the flattening of inherited tables ( you'll see the extended/child table in the AOT but it has vanished in the SQL database ), being SURE you have change tracking disabled on your database prior to running the "Data upgrade checklist for in-place upgrades", or now the deployment of AIF inbound ports which extend SysOperation framework.  We'll share our experience so that you can save a few grey hairs!