ContributionsMost RecentMost LikesSolutionsInvoice number sequence changing We are experiencing an issue after having changed our Invoice numbering sequence in AccountRight. Here it was changed and what is now taking place (I'll use example numbers): - Our numbering sequence was up to 10000 - We then changed it start at 30000 - All newly created orders correctly obtained numbers in that sequence (E.g. 30001, 30002, 30003) - However, if we invoice any of the old orders (E.g. 10123), then the next NEW order we create is grabbing a number from that sequence, rather than the 30000 sequence. Is there any way to stop this from taking place? We're essentially stuck in a loop, with loads of duplicate order numbers taking place, as the sequence keeps flipping back and forth. We have a very high volume of daily orders (200+) with some not being invoice for weeks at time. Therefore it's seemingly impossible for us to rectify this, as we need to keep going back and invoicing orders from the old sequence. How do we solve this? SolvedRe: All registered apps have disappeared Anyone receive any meaningful updates on this? We haven't. And now the Developer Portal is displaying an error ("We have encountered some issue, please try again later or contact support") which is preventing us from even being able to attempt to register a new app. We've literally gone backwards from where we started earlier today, with essentially no help from support. Re: All registered apps have disappeared The update we received is that our app integration 'expired' in Feb of this year. There was zero communication to us around this. I can't even find any documentation anywhere stating that registered apps expire after a point in time? This would require new keys to be issued (which isn't automatic) and approved (which also isn't automatic), a production deploy of the new keys on our side AND every one of our customers to disconnect/reconnect their MYOB integration inside our platform. As it stands, our integration is still down and we're struggling to get any meaningful assistance from the support teams. The first reply to our support ticket simply said 'Expired'. Nothing else. A single word. That was it. All registered apps have disappeared Our API integration suddenly stopped working for all of our customers. We are receiving an error for a missing/inactive key. We logged into our Developer account to find ALL registered apps were no longer there. How do we get assistance restoring these, as they were not deleted by our team but have somehow disappeared, rendering our integration broken. This is kinda terrifying... MYOB API Speed / Slowness Hi All, Our product integrates with the MYOB AccountRight API in order to enable the automatic creation and updating of Quotes/Orders/Invoices. Essentially, customers create and manage their Quotes/Orders/Invoices inside our SaaS platform, which then updates MYOB. We experience considerable slowness when creating/updating orders via the API. This slowness is also entirely disproportionate to the size of the call (I.e. an order with 1 line item may take 30-60 seconds to create/get a response back from the API, while the next order with 10 line items may take 5 seconds). We also experience frequent Gateway timeouts when sending calls. Is this common? Is the API generally this slow for basic calls like order creation/updates? Our other accounting package integrations, such as QuickBooks, see almost instantaneous responses when dealing with their APIs. We're at the point where we're considering recommending new customers coming onboard switch from MYOB to QBO or Xero, as we receive a lot of backlash on the slowness of the integration. Any thoughts on what's causing this, or what can be done? Thanks, Paul Adding/rotating API keys and secrets Hi all, I'm wanting to add new API key-secret pairs for our application and eventually retire the existing ones. I had a few questions: 1. How do I add keys and secrets? Do I need to hit Register App in the dev dashboard? 2. Will the new pair be immediately useable? If not, what are the next steps? 3. Will the other pairs remain valid? 4. How do I invalidate a key-secret pair? Regards! SolvedIncorrectRowVersionSupplied error when creating order/invoice for first time Hello, Our platform integrates with MYOB via API in order to allow our customers to automatically create/update MYOB orders and invoices. Orders created in our platform are passed to MYOB. Amongst a number of issues that we face with this integration, we have one that is confusing and stumping us. Issue When we create an order or invoice for the first time (E.g. sending the data via POST request for a NEW order, not an existing order) we sometimes receive an IncorrectRowVersionSupplied error. We don't understand how this can happen during the first submission? Typically this request works perfectly fine and MYOB returns the corresponding Order #. With higher volume customers, we see this error daily. Resubmitting the request usually results in it being processed successfully, however, this is not an ideal experience. We'd appreciate any assistance possible. Paul