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
|
If you want to make sure that a function implemented via the SysOperation-framework is always executed via batch processing, you can set the SysOperationExecutionMode to ScheduledBatch (e.g. via the MenuItem of the controller - see here).
If this is a function that requires a user dialog, however, the problem is that the "Batch" tab is displayed by default and, for example, the "Batch" check box is not activated there.
Of course you can activate this checkbox by including a call to parmBatchExecute() in the UIBuilder:
However, one still has the problem that the user could deactivate the checkbox in the firm conviction that this would not send the function to batch processing.
If you want to prevent this, you can overwrite the method postRun() of the UIBuilder as follows:
This looks as follows in the dialog. Now the user can see that the function is executed in batch.
Alternatively you could deactivate the whole register Batch in the postRun(), but then you cannot specify a batch processing group anymore:
It would look like this: