AX Locking and Entry Assignment


I am completely new to AX and have question about performance… I am reading “Data Model Documentation” and found this description for a field:


Special field created to the table to reduce locking problem what slowed down AX posting procedures. Field gets random number from 0 to 19 generated based on user session id. It reduces probability by 20 times that one user needs to wait for another user while update has been carried through in the relevant line. In AX version 2.5 there was no this mechanism and it caused performance problems due to the SQL locking. For analyses purposes this field should be ignored while aggregating data. For that reason special views are created where this field is excluded.

But how was the problem with RecId resolved for LedgerTrans table. Is RecId sequential? Does it skips numbers if error happen during transaction?