integration

Building Your Own Export Framework with Dynamics AX (part 2)


Today, I want to pick up on this blog series we began in early January.  If you’re just picking up on this now, the previous post details our motives for building an entirely new and light-weight export functionality – avoiding flat file integration, we can support direct-to-API eventing because AX 2012 is just that powerful.

The case for SysOperation: Internal + External Consumption


Model View Controller

For those of us who have developed on earlier versions of AX, RunBaseBatch rings a bell.  In fact, it was the primary ( and frankly is still used by Microsoft in 2012 R3 ) means of scheduling code execution.  It could be an hourly process to invoice sales orders, a nightly MRP run, or a complex financial consolidation. The problem was it still had to execute in native X++ albeit on the Server tier, and if you had an external application that also needed to execute the same logic you had to build an extra interface.