Comments
Here the exact description of the current behavior: If we have a sales order line and a flexible batch reservation has been made for a sales order line AND then this line is mixed with other lines (without flexible batch reservation) in the work, the work is simply no longer carried out automatically despite the work template setting. It is then only possible to do this with the Warehouse Management App. Simply means that despite the work template setting (Valid Automatically process = Yes) the work is not carried out automatically. This work cannot be closed via the “All Work” module either. It is then only possible with the scanner.
Since Microsoft has found a way to clean up standard Business Central apps, the next logical step would be to allow third parties to do the same—ideally, at the same time during the Step version update. Currently, many tables, schemas, and even some Enums are awaiting removal. For example, if an Enum is used in a field, the field cannot be removed, which in turn prevents the removal of the Enum.
I fully agree with this post. Over time, table and field ranges will fill up with Removed tables and fields, which not only adds needless baggage to the app, but also make the app less maintainable. Microsoft has already conceded that point, and they are planning a cleanup in BC26 (2025 RW1).There will need to be some rules for this, as there are for existent breaking changes. You will need to have published at least X version(s) with the removed field/table in order to give extending apps time to update their data.