GetLatestNumberSequence API returns incorrect transaction number sequence seed and device activation gets stuck


Symptoms


GetLatestNumberSequence API returns incorrect transaction number sequence seed and device activation gets stuck

Resolution


The solution is to update the storedproc "GetlatestNumberSequence" to bring the MAX transaction ID instead of the top record from the salestransaction table based on "CreatedDateTime"

More information


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.