When you have a number sequence that is set to continuous and the number that pulls into the form is 000000 and is not a valid number.
This is caused by the Stored Procedure not getting updated when the R2 in place upgrade process is complete. We suspect that this problem may be due to incorrect steps done during the upgrade that we are not able to reproduce.
This blog describes the steps on how to copy the stored procedure from a working environment to resolve the issue with the no value pulling from the number sequence table.
To copy out the stored procedure from a working data base you will use the following steps.
9. Select all and Copy the code
Now in the non-working data base you will do the same steps but you will paste the code into the stored procedure. You will need to change the top line to use the database name that is not working.
Then you can execute the code by clicking the Execute button.
Please make sure you have a backup of your data base before you try these steps. You will need to restart the AOS and AX after you have run this code.
If you are still having an issue with the Number Sequences not advancing you will then want to check the permissions on the stored procedure.
Here are also the steps to do this:
8. Select Permissions and check the permission setup for the user.
Test adding the user that is currently logged on to the list and ensure that the Execute option has Grant marked
Go back to Microsoft Dynamics AX and test that the number sequence is now working.
Thanks a lot!
I had the error that NumberSequence::getNextNumber method always returned zero after R2 upgrade.
Copying getNumInternal stored procedure from a correctly upgraded R2 instance did the trick.
you saved our team from the big trouble....
Great! Save a lot of trouble......thanks
This helped me in fixing the number sequence problem. Thanks a lot.