All of a sudden the next and previous menu buttons no longer work when using the Orders form 42. First and last work. Searching works. Also, if you pull up the Orders list, the next and previous work fine there - so not likely a problem with the table keys and changing the sort does not help. I restarted the Nav service - no better after that. There are no filters and the TableView properties of the form look fine. So, no matter what order record I am currently on, previous button does nothing, next button starts a new record. One exception - deleting the current record takes you to the next record. Any ideas?
What would Elvis do?
0
Comments
Pargesoft
what is NAV Version ?
is it not working in both classic or RTC ?
S.V.Sudhakar
are you trying to ask,how to assign roles & permission to particular user ?
Create role and assign permissions
open NAV Tools-->Security-->login id-->Roles
Synchronize login.
S.V.Sudhakar
Regards
PBA
I have tried debugging and the debugger does not allow access at the point of grabbing the next record even with breakpoints on triggers. The debugger picks up at the point at which it is already on the wrong record or creating a new one depending on whether next or previous is used.
At the point the debugger gets to OnNextRecord it is already on the wrong record. Also, I have tried removing all code and variables there.
Version is 2009. This problem only exists in the classic client.
Pargesoft
best
Bruce Anderson
Try again because thats the reason why it's not working. You can't have any code and any (yours) variables in trigger OnNextRecord because this means that you want to handle OnNextRecord manualy. Also clear code in those triggers if you have two or more empty lines also delete them. Do not delete Steps variable - it is standard variable.
Regards
PBA
I have plenty of forms with code in the OnNextRecord that work just fine- that was definitely not the problem. I had removed all that code and the variables anyway.
In the end, it turned out to be a corrupted form. I have NEVER seen this happen in the older version but somehow this form was damaged and there was no indication of anything wrong. Comparing text export to a fresh copy showed nothing wrong but when I replaced the form with the fresh copy the problem went away even after re-applying my customizations.