Summary: For the purposes of small or medium data migration (data conversion) where performance is not a concern Excel can be used for import of ledger transactions into Microsoft Dynamics AX 2012.Challenge: Data model changes in Microsoft Dynamics related to high normalization and introduction of surrogate keys made import of customers more complex.Microsoft Dynamics AX 2012 provides an easy to implement framework to generate custom number sequences.
Number Sequence Table number Sequence Table; tts Begin; select for Update number Sequence Table where number Sequence Table.
Also this record versioning is used to determine if a cached record entry in the AX memory / file space has to be refreshed.
You may read up more about this on the following link: https://msdn.microsoft.com/en-us/library/bb190073By updating a record directly in SQL Server, the Rec Version field is not maintained, and if your AX AOS is running, it will not be aware that the record has been updated. Here are the details about record caching on MSDN: https://msdn.microsoft.com/en-us/library/bb278240In AX many of the fields have a numerically increasing value that we refer as Number Sequences.
Each row in Microsoft Dynamics AX database within Microsoft SQL Server has a unique identifier which is by default the primary/surrogate key as well for the records.
The field is called Rec Id, and it is maintained as an incremental, int64-based positive or negative number.