Let’s have a look at what our code changes will look like in the D365 user interface, before scheduling the actual batch job:
Analyzing this dialog, we will see that it looks like every other batch dialog, with only one parameter: a file.
Below, we will see the code which is taking care of the design and functionality for this batch process.
The controller class
/// <summary>
/// Controller class for creating & posting PO packing slips
/// </summary>
class AXMPostPOReceiptsController extends SysOperationServiceController
{
/// <summary>
/// Creates new instance of <c>AXMPostPOReceiptsController</c>
/// </summary>
public void new()
{
super();
this.parmClassName(classStr(AXMPostPOReceiptsService));
this.parmMethodName(methodStr(AXMPostPOReceiptsService, processOperation));
this.parmDialogCaption("Create packing slips");
}
/// <summary>
/// Sets the caption of the job
/// </summary>
/// <returns>Caption of the job</returns>
public ClassDescription caption()
{
return "Create packing slips";
}
/// <summary>
/// Method which is run while calling the corresponding menu item
/// </summary>
/// <param name = "args">Arguments passed from the menu item</param>
public static void main(Args args)
{
AXMPostPOReceiptsController controller;
controller = new AXMPostPOReceiptsController();
controller.startOperation();
}
}
