Comments
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.
We have this exact problem with one of our customer.He is in retail a lots of transactions are with credit card.Depending of the hour of the transaction, the bank record the transaction on the same say or the day after.So he can have multiple bank lines for multiples transactions.He can't do many-to-many matching and even if the total balance to 0 he can't post because each single match are not balanced.I now have to tell him he can't do his reconciliation in BC...