Receiving this error when trying to link customers on simPro to MYOB. Only started today (I have been on holidays). Upgraded to 2022.8 (AccountRight Plus) yesterday.
<b>Error response from MYOB:</b>
[Code: 173] A request should not contain UID during POST operation
Exactly same issue with NETO/Maropost Cloud MYOB integration. Started on/around Monday 12th, same error.
I'm getting the same error message after doing my update too.
To all: see https://apisupport.myob.com/hc/en-us/articles/5319928281871-Changes-to-POST-requests. API changes since 2022.8, 3rd party addons will need to change their interactions with the API.
Has anyone managed to resolve this? From what I've read, I'm still not sure what I need to change in simpPro to transfer customers from there to MYOB. Nothing I've changed has fixed the issue.
It seems a bit odd as it's only happening to a few new customers, not all of them.
Maropost is aware
but the more noise the better to get it done faster!
Yes just got off the phone to SimPRO myself and they have advised I am 'lucky' because at least my customer payments are going through. Doesn't help that none of the customer contact details are exporting. They are aware and trying to resolve. No advice as to when, just that they will advise.
Ok - this is now beyond frustrating and extemely questionable. MYOB says they can't do anything and the 3rd party is required to contact them in order to fix the problem. SIMPRO says its an error MYOB end and that they are working with them to rectify the matter - so I assume they are in contact with MYOB. We are now paying for 2 products (MYOB and SIMPRO) that we have not been able to use to its full capacity since 8 September 2022 - almost 1 month. I also find it unusual that we have never been contatced by either party advising there has been an issue with our builds.
Hi FA_CM , it's not strictly an error at MYOB's end, but it is a deliberate change to previous API behaviour, which has caused several add-on programs to throw errors instead of just working. This change was announced some time (maybe a month or two?) before it was implemented, but the implications may have been missed.
Besides, it's hard to test against a change which has not been made. MYOB bear some responsibility; maybe a new version of the API should have been made available (separate version number, heavily publicised) before sunsetting the current version. That would have given all developers time to make their changes.
i am in the same boat as well with Neto/Maropost
causing huge problems when i cant get information out the system
