8
The current primary keys of the ledger entry tables are of the data type Int32. The 32 bit integer leads to the problem that only about 2.14 billion items are possible at most.
Another problem is the redetermination of the entry no.: The new number of the ledger entry is searched for according to the scheme highest number + 1, which leads to a table lock every time it is inserted.
It is similar with the field transaction no. in the item tables. That is also an Int32.
Another problem is the redetermination of the entry no.: The new number of the ledger entry is searched for according to the scheme highest number + 1, which leads to a table lock every time it is inserted.
It is similar with the field transaction no. in the item tables. That is also an Int32.
STATUS DETAILS
Needs Votes
Comments
There should be a provision of updating the primary key if needed. There are scenarios where we may need to change primary key, and for that we need to delete the entire table and re add it. which can cause a lot of data disruption. So there should be a provision to change primary key directly.
Category: General
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