There is an issue when you set more than one No. Series for any document / master.
When a record (master / document) has been assigned with a number and you click the ellipsis next to the No. and select any No. Series, system will prompt you whether you want to continue the update. If you click No, the selected No. Series will still consume one number (Last No. Used will increase by one) even though the action is supposed to cancel the update. In addition, this Last No. Used can be found no where (neither in the table nor Change Log Entries) because the number is never inserted into the system.
The No. being the primary identifier of any records in the ERP system is important and critical. Any unaccounted-for number in the system may cause an alarm and red flag in the audit. The implication is more severe when you set to use the same No. Series for unposted and posted documents because that would mean you have a missing number in the posted document which can never be found in the Change Log Entries or unposted / posted tables.
This issue can be reproduced in sandbox and production without any extension.
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team