How to run multiple sequential batch tasks using SysOperation framework

(0) Share

Report

Posted on by Community Member

Calling technical Batch gurus! (RunBaseBatch, SysOperation frameworks)

Our customer has a batch operation that has been developed in the SysOperation framework, with typical Controller/Service classes. They would like to manually create a single batch job that calls the operation several times with different parameters, and have each task execute in sequence (each task is dependent on the previous task completing).

The RunBaseBatch (older) framework enables behavior like this with methods that can be overridden (canGoBatch, canGoBatchJournal), but the SysOperation framework does not have the canGoBatchJournal method, and doesn't appear to share this ability. When I attempt to set this up manually using the controller class as the entry point, the warning "The specified class is not fully designed for use in the Batch job form" appears (see first image). It sounds like this can be reconfigured to work, but I couldn't find anything helpful online for this edge case.

What's more interesting is that this can be set up to work with X++ code, by using the generic SysOperationServiceController, and passing the specific controller/service upon construction (see second image). This results in the desired behavior and the code runs as expected (see third image, ignore that the service class failed). Unfortunately, there doesn't seem to be a way to configure it this way from the browser UI.

Thanks for reading. Any suggestions are welcome!

I have the same question (1)

All responses (3)

Answers (1)

reachnaidu 890 on at

Like (0)

Report

Hi Sawyer,

Pleae submit a support incident if you have still have no resolution.

Was this reply helpful? Yes No
Verified answer

Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi Sawyer,

For SysOperation framework you can use attribute SysOperationJournaledParametersAttribute instead of canGoBatchJournal method.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Thanks all, the [SysOperationJournaledParametersAttribute] is what I was looking for, and successfully enabled the controller as a valid class for batch tasks.

This blog post contained additional information that I needed, specifically the new method on the controller. The existing implementation did not override new(), instead using a static construct method. Because the class name and method name were not set in the new method, the default UI builder did not have knowledge of the contract class, so the parameters couldn't be set on the batch tasks. Using the new method as documented in the post solved this.

Was this reply helpful? Yes No