Thank you for visiting our Partner Zone. This area is an exclusive space for MYOB Partners. Find out how to Partner with MYOB.
May - last edited May by Steven_M
My client is unable to open 2 employees card files and this is the error script, i have seen that this was resolved on a previous query by MYOB running a script?
AccountRight Application Error Report
Application Version: 2019.1.22.366
Application File Version: 2019.1.22.366
Incident Id: 7318fe68-2b21-4293-a8d1-f15850d27b62
Time: Wednesday, 8 May 2019 8:41:09 AM
1 : MYOB.Huxley.API.HuxleyApplicationException
MYOB.Huxley.API.HuxleyApplicationException: (Unknown): ShowUIView(CardDetail,...,...) ---> MYOB.Huxley.API.HuxleyApplicationException: (DataNotUniqueError): More than one EmployeePayrollDetails exists for employeeId = 2188
Solved! Go to Solution.
We would need to look at running a script over that company file. So we can do that can arrange for that to occur can you confirm the following information:
Where the company file is stored i.e. online or local
What the LAST FOUR DIGITS of the serial number is - Setup>>Company Information
What is the company file ID - Help>>About AccountRight
The file is online
Ill advise the client of the action you will take so they are aware. Will they need to be out of the file?
Thank you for confirming that information
I've run the necessary script over the company file for you. This should allow you to open those employee cards.
Just on a side note, the error has been linked to the Add Payroll Category button in the Pay Employee window and in particular, the Save changes for future pay runs option. My recommendation to limit this message from occurring is to:
Let us know how you get on and if you require further assistance with this issue
Yep working now thanks Steven.
Also do you know if this will ever be fixed as i beleive it is an ongoing issue and i cant see why you wouldnt be able to update whilst in the pay run especially when they have up to 90 staff to do a pay run for.
Thanks for you assistance
It has been something that we have raised with the required team and are still awaiting a resolution for. As indicated in my previous post on this thread we do recommend following the process outlined where possible to limit the chances of this message occurring.