DazzaB
Experienced Cover User
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: OrmDataException
I have been getting ORM Data exceptions myself on and off for a while and it appears to be only in my Sales area. Have yet to see it in Purchases If you ok the ORM exception and then try to record the Invoice again you will end up with 2 ( or more if you continue to repeat the procedure ) recorded invoices that are identical except for them having consecutive invoice numbers It appears to be related to the recording/printing of the invoice and we can get it happening several times a day we have found that if the error occurs then go and check to see if it has been recorded and then reprint that copy and return to the still open invoice and delete it Deleting and restarting the Invoice from scratch is a very very poor alternative as you may have multiple lines of information that would require reinputting Myob Ivory tower needs to get its head out of the "cloud" and fix the bug and quickly My guess it has to do with the flag for the invoice having been recorded not being updated to show that it has been so the computer looks at the invoice onscreen as being a new invoice to be input and hence uses the next invoice number Please advise me as to what the actual error cause is please This is what has been touted as the cause This is not true "Generally speaking an “ormdataexception” message means that the data has been changed in the background. This could happen if a transaction was opened in two windows or on two computers and it was changed on one, whilst the other computer it was still open" as when this happens the message tells you that the data has been changed and you cannot record your copy. A simple fix for that issue which is a problem yet for the "TOWER" to fix would be to have only the first person with the invoice open to have editting rights and the other person to only have read only and it to advise the second person that it is read only and lock the screen so no editing can be done. Common sense would also have it 1. advise the first person logged in that somone else has logged in and who it is and also for 3rd/4th 2. advise the second and possibly 3rd/4th read only person who else is looking at that invoice/order and who is the editting person 3. then when the editting person completes their edit the read only people are advised that it has changed and it could either automatically update the invoice/order and unlock editting for person #2 and update #3 and #4 advising them who is now editting it or It may make more sense to just tell #2 #3 #4 etc that a new updated copy is now available and to see it/edit they need to call up a new copy. As the old now obsolete copy is only read only it could be left up as a comparison against the now updated version1.3KViews0likes1Comment