Hello fellow developers,
I’m adding this note here in case others are encountering similar behaviour. We’ve identified a separate issue to what is primarily being discussed here. Certain endpoints, such as /GeneralLedger/JournalTransaction, fail to return complete data when paging is involved (i.e. using $top and $skip parameters). Through support case #46197, MYOB has confirmed the issue is reproducible internally.
Hello MYOB team,
I appreciate the ongoing engagement here, and through the support cases we have open, however I question why there is still no public acknowledgment of this on the MYOB status page under Developers -> API (https://status.myob.com/).
As developers, we’re on the front line with customers who expect clear communication about what’s broken and when it will be fixed. This issue has now been active for over a week. My first report from a customer came through last Thursday and it’s becoming increasingly difficult to maintain trust when the only message we can offer is “we’ve escalated it to MYOB,” while the official status page shows no indication of a problem.
I’d like to respectfully request that confirmed issues are publicly acknowledged and backdated on the status page. Otherwise, it undermines the purpose of having a status page at all. Transparency is key, not just for technical teams, but for the businesses relying on us to give them honest, timely updates.
Thanks again for your support, and I hope this can be addressed soon.
Cheers, Shem