- The article discusses the importance of effective task management in enterprise resource planning.
- Prior to the introduction of "Priority Based Scheduling" in Microsoft Dynamics 365 for Finance and Operations (D365FO), administrators could designate batch servers to a batch group with more flexibility.
- Overutilization of tasks can lead to strain on the system and performance issues, as seen when 98 tasks with "normal" scheduling priority executed simultaneously.
- The older batch group mechanism allowed for limiting the number of batch servers assigned to a batch group to control parallel tasks, but this control was seemingly lost with the shift to "Priority Based Scheduling."
- Version 10.0.38 PU63 introduced a new feature called "Batch Concurrency Control" to limit parallel tasks in a batch group, helping to prevent system strain and maintain performance.
- Activating the "Batch Concurrency Control" feature adds a new field in the batch group settings for managing task concurrency effectively.
- Setting the value to zero in the batch group setting means no concurrency control, while setting it to -1 halts all batch jobs in the group.
- The implementation of "Batch Concurrency Control" in operations mirrors the previous strategy of selecting few batch servers for a specific batch group to throttle tasks and ensure balanced system load.
Registered users can view the full text for FREE!
Sign In Now!
