This post is machine-translated. The original post in german language can be found here.
These post applies to following version:
Dynamics AX 2012
Dynamics AX 2012
|
|
|
|
|
|
This post is machine-translated. The original post in german language can be found here.
These post applies to following version:
Dynamics AX 2012
|
Anyone who has ever implemented a function using the SysOperation framework knows that creating the necessary (up to) four classes is some work.
For
lazyefficient contemporaries I have therefore developed the following job, with the help of this time-consuming work can be significantly shortened.In the job you have to set an "base name", which is used for naming the four classes (Controller, Dataprovider, UIBuilder and Service).
In addition there is a map called dataContractParmsMap from - unless you have inserted content in this map - matching parm methods are created when generating the data provider. In example job the map contains two entries for a customer account number and an item number.
How these classes will look like and which methods are generated, the above screenshot is showing.