When retrieve periodic journal to create AP invoice journal, following error msg comes up frequently. The error will disappear by clicking “CTRL+F5”, but it comes up quite often, so need a solution for this.
Error msg:
“Cannot edit a record in Journal lines (LedgerJournalTrans).
The values displayed in the form are not current, so an update or deletion cannot be made.
To view the current values, on the Command menu, click Restore or press CTRL+F5.”
That’s an update conflict. Before you saved your changes, some other person or a piece of code changed the same record. If you were allowed to save your changes, the concurrent change would be lost and data consistency would be compromised.
If you believe that it’s caused by some code and not by user updates, get a developer to look at what’s writing to the record.
Is there any way to stop this error message?
I found out that after retrieving the journal, if you close the journal line window and open it up again to edit,
the error message didn’t pop up. Do you think this could be a solution?
If there are any better or quicker solution, please let me know.
Any solution to this, I am still getting the same issue while modifying the journal retrieved from periodic journal
If it’s a regular update conflict, where two persons try to edit the same record at the same time, it’s just normal behavior of multi-user systems. If two users try to edit the same file in Windows, it wouldn’t work well either. If you often get into these problems, considering reorganizing your business processes, so people don’t try regularly update the same record at once. Another approach is introducing locking, as you can see in journals.
If you get this error because of a bug in code, find the problem and fix it. For example, if you read one record two two buffers and then try to update both of them, the second update will fail because it would overwrite changes of the first update. The solution is using the first buffer of the second update, rereading the second buffer, merging both updates to a single one or something like that.
I am getting the same issue in all journals in ax2012 using a single user modification at a time. I am entered several lines in the journal, change the date in lines getting me this error
Then I would debug the code to see which two updates are conflicting (after verifying that it isn’t a known issue; in that case you can simply install the hotfix). If it’s a standard application (without customization), you can also create a support ticket with Microsoft.