I keep getting this error message when I am trying to link MYOB to LEAP. Anyone know how I fix this..
[Name] - UidInPostBody, [Message] - A request should not contain UID during POST operation, [ErrorCode] - 173, [AdditionalDetails] - .
Its a problem with MYOB. it started a few days ago and hasnt been fixed. i have the same problem and we dont use leap.
Same here. not sure if it is MYOB issue or LEAP's?
just checked with LEAP, there is technical issue in LEAP at the moment. they are fixing
Hi Everyone,
Thanks for your posts. If you're experiencing an error when trying to connect Leap to MYOB, this is something that you would need to check with Leap as it is a third party software integration.
Do let us know how it goes.
im not with leap and having the same problem. have been connected with myob for years and the problem started a few days ago.
Hi morgans1,
If you're not with Leap and having issues with your MYOB software can you please start a new post with information on what you're experiencing so we can take a look into this for you.
On Fri (09.09.22) LEAP were saying it's a MYOB problem....now MYOB are saying it's a LEAP problem. What are we meant to do?....
This was on LEAP announcement page just this morning :
"Dear LEAP Users,
As of Friday, the 9th of September 2022, users are experiencing issues with syncing MYOB journals from their General Ledger Link to MYOB.
Affected users are experiencing the error: "[Name] - UidInPostBody. [Message] - A request should not contain UID during POST operation. [ErrorCode] - 173, [AdditionalDetails] -. "
We thank you for your patience as our team have investigated this error and liaised with MYOB. MYOB has acknowledged this issue and are currently looking into it.
Please refer to the MYOB Status page for updates on this particular issue: https://status.myob.com/incidents/399888
Furthermore Smiley70 when you click on that MYOB status link that LEAP posted it is very vague as to what it relates to. It does not suggest it is the LEAP/MYOB integration problem. Hopefully we get some clear answers and a resolution soon.
Hi Melisa_D (MYOB Moderator) as you can see from the updated posts, it has not gone well. LEAP now advise that MYOB are working on the issue at their end. The MYOB status link they provided give us no answers. Can we please have clarity and confirmation as to when this issue will be fixed?
Thank you.
Hi Everyone
As has been indicated, we are aware of a situation that is impacting account management and online use access management. Our teams are currently investigating that situation and we posting updates, when they come to hand, via our Status Page: status.myob.com - at this time, we don't have a timeframe for resolution.
While we aren't aware of any widespread third-party API connection errors, depending on your solution and how it operates you may be impacted by that aforementioned situation on our Status Page. As with all third-party solutions we do recommend speaking to the third-party provider to get assistance with that product. Those third-party solution providers do have a support point that can be used to get further assistance with their product's connections.
Our software is experiencing the same issue. Our clients won't be able to continue their processes because of this issue. So we had to find what causes the issue. We noticed that it occurs only on order line items with special characters in it.
For our case, a manually entered products contains $ (dollar sign), so we just had to removed it and the issue was gone. Hopefully MYOB fix this, it used to work but not it doesn't. But for temporary work around, this might work. Hope it helps
