Forum Discussion

JohJohB's avatar
JohJohB
Experienced User
2 months ago
Solved

DataNotUniqueError - Employee Card Issue

Again it seems there has been a double up in the back end of our employee card files and I am unable to edit an employees details.  Is there anyone that can run the script in the backend to rectify this issue.  This isn't the first time it has happened.  It would be good if there was a way I could rectify this direct and not have to rely on a community chat forum for someone from MYOB to answer.

 

"MYOB.Huxley.API.HuxleyApplicationException:  (Unknown): ShowUIView(CardDetail,...,...) ---> MYOB.Huxley.API.HuxleyApplicationException:  (DataNotUniqueError): More than one EmployeePayrollDetails exists for employeeId = 4160"

  • Hi JohJohB,

    I've arranged a script over your file that should fix the issue. For your future reference, I would like you to know that the error happens because the same employee information gets saved twice by mistake. This occurs when you make changes to an employee's pay and tell the system to remember these changes for next time. Doing this incorrectly can cause the system to get confused and show an error when you try to view that employee's details again.

    I hope this helps!

    Regards,
    Earl

2 Replies

  • Earl_HD's avatar
    Earl_HD
    MYOB Moderator
    2 months ago

    Hi JohJohB,

    I've arranged a script over your file that should fix the issue. For your future reference, I would like you to know that the error happens because the same employee information gets saved twice by mistake. This occurs when you make changes to an employee's pay and tell the system to remember these changes for next time. Doing this incorrectly can cause the system to get confused and show an error when you try to view that employee's details again.

    I hope this helps!

    Regards,
    Earl

  • JohJohB's avatar
    JohJohB
    Experienced User
    2 months ago

    Thanks Earl. 

     

    I appreciate you fixing the issue so quickly.  I'm not sure how checking the box "Save changes for future pay runs" can be done incorrectly.  However,  next time I'll make sure I just ignore that feature and change it manually.

     

    Regards,

    Jo