All Dear Readers,
Hope you are all doing great!
Let’s start with another useful article! Limitation of Auto Split Key in D 365 Business Central.
Note: – This document contains the solution for Dynamics 365 Business Central Standard Errors, the line cannot be split and there is not enough space to insert the correction line.
The First error occurs when adding a new line such as adding a sales line.
The Second error occurs when we undo a posted document as undo posted sales shipment.
As shown in the debugging result, this is caused by ‘Line No.’.
Both errors occur because of a single property which is an automatic numbering feature in Business Central.
[AUTOSPLITKEY Property: – Sets whether a key automatically
created for a new record placed between the current record and the previous record.
To use this property the following condition must be fulfilled.
When we add a new record between the current record and the previous record, new numbers are automatically generated with this property.
For Example, If the Line No. starts from 10000.
And the next Line No. is 20000.
When we add a new line between these two lines, The autosplitkey property will automatically create in between No. for the new line.
The Line No. is 15000.
Furthermore, if we continue to add new lines, the number will be automatically assigned by the autosplitkey property like 15000 -> 12500 -> 11250 -> 10625 -> 10312 -> 10156 -> 10078 -> 10039 -> 10019 -> 10009 -> 10004 -> 10002 ->10001 -> After that the error occurred because we added new Lines 13 times in the same direction.
This does not mean that we can only add 13 times in the same direction, it depends on the margin between the current and previous record.
But we should remember that adding lines between two records will not be unlimited.
This is almost the same in posted sales shipment because when you undo the post-sales shipment the system will automatically add a new line with -1 quantity, if the number is no longer then the error will be prompt.
If we use system functionality in a normal way, then these two errors occur rarely. But if we create or import data through a configuration package, It may cause a problem.
If we face this issue anywhere then we can: –
We hope this write up will help you to grow!
Stay connected with us to learn more!
Thanks to all.