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.

Financial Dimension Control with no data source

Financial Dimensions in AX6 have been revolutionized, as many of us know.  Adding them to a form is rather simple, given that one of your underlying data sources has a Default Dimension field.  But, what if you were building a form that didn't meet this requirement, or better yet had no data sources at all?  This is where the DimensionDefaultingControllerNoDS class comes in to play.

First thing's first: add the class to your form declaration: