---

RunBase vs SysOperation

The RunBase and SysOperation frameworks are two different frameworks in Microsoft Dynamics AX and Microsoft Dynamics 365 Finance and Operations that are used to develop batch processing functionality. Here are the differences between them:

1. Architecture: The RunBase framework is a legacy framework that was introduced in earlier versions of Dynamics AX, while the SysOperation framework is a newer framework that was introduced in Dynamics AX 2012 and is still used in Dynamics 365 Finance and Operations.

2. Object-oriented: The SysOperation framework is an object-oriented framework, while the RunBase framework is not. This means that the SysOperation framework is more modular and easier to maintain and extend than the RunBase framework.

3. Extensibility: The SysOperation framework is more extensible than the RunBase framework. It allows developers to add more input and output parameters and define their own customizations through the use of events and delegates.

4. User interface: The SysOperation framework provides a better user interface experience than the RunBase framework. It allows developers to create custom dialog boxes with a modern look and feel, and it supports the use of grids and other controls to present data to users.

5. Migration: Microsoft recommends that developers migrate their RunBase-based batch jobs to the SysOperation framework in Dynamics 365 Finance and Operations. This is because the SysOperation framework provides a more modern and flexible approach to batch processing, and it aligns with the overall direction of the Dynamics 365 platform.

In summary, the SysOperation framework is a more modern and extensible framework for batch processing in Dynamics 365 Finance and Operations, while the RunBase framework is a legacy framework that is still supported but is being phased out. Developers should consider migrating their RunBase-based batch jobs to the SysOperation framework for improved functionality and long-term support.

---

Feature	RunBase Framework	SysOperation Framework
Architecture	Legacy framework that relies on the RunBase class hierarchy.	Modern framework that is based on the Command and Query Responsibility Segregation (CQRS) pattern.
Class Hierarchy	RunBase framework uses the RunBaseBatch, RunBase, and RunBaseReport classes.	SysOperation framework uses the SysOperationService, SysOperationServiceController, SysOperationServiceContract, and SysOperationServiceProcessor classes.
Object-oriented	Not fully object-oriented.	Fully object-oriented.
Extensibility	Allows customization, but not as extensible as SysOperation framework.	Highly extensible, allows for easy customization through the use of delegates and events.
Parameters	Requires the use of several classes to define input and output parameters.	Allows developers to define input and output parameters using the Data Contract and Data Contract Attribute classes.
User interface	Provides a basic user interface for defining batch jobs.	Provides a modern user interface for defining batch jobs with options for creating custom dialog boxes, progress dialogs, and more.
Exception Handling	Requires custom code for exception handling.	Provides built-in exception handling through the SysOperationException class.
Integration with Workflow	Cannot be integrated with Workflow.	Can be integrated with Workflow.
Code Migration	Requires a significant amount of manual code migration for batch jobs.	Supports easy migration of code from RunBase framework to SysOperation framework through the SysOperationMigrationService.

Note: The above points are based on the comparison between RunBase framework and SysOperation framework in Dynamics AX 2012 and Dynamics 365 for Finance and Operations. Other versions of the software may have some differences in features and functionality.

---