ContributionsMost RecentMost LikesSolutionsRe: Update to MYOB Developer Program Terms and Conditions " we've advised users that an update is required by 28/02/26, and we're sending instructions" That is the first I have heard of a specific deadline of 26/2/26! I have been storing a list of files including file Id based on the Company Files end point will/have to continue to do so for those users still not online. I will have to change code to bypass that process. For users with multiple files, it is not a matter like or dislike, it will be essential to create a list based on the files they have authorised. Some of them run automated batches of imports that import into more than one file so there is no possibility of a user being on hand to authorise each import. Both the above date and the instructions should have been published months ago! Re: Update to MYOB Developer Program Terms and Conditions This is all a bit vague. I get that from March all my users will have to redo authorisation at least once every 12 months and I can send them an email telling them to do just that but at the moment all my apps are set up for the old process. Should I be telling them to redo authorisation before some date in March? I also get that I will need to amend my applications to replace the scope with a list of more specific scopes and the resulting authorisation will be for a specific company file as identified by a business Id/guid. If the users applies the app to more than one company file then the app will need to securely store authorisation details including business Id, code and refresh token specific to each file. At present my apps get a company file list via the Companies end point and put it in a combo box so they can select the file. I gather that option will cease to be available so the company file selection will have to be from the above list generated via the authorisation process. I am working on adapting the apps to do it that way but feel it would be nice if someone would provide a specific deadline for implementing this, preferably not too imminently. I have raised support tickets asking for more details and specifically this question and received no reply, only occasional snippets of information about how it will work being added to the online documentation. Re: Edge appearing without warning after repeating online authentication Both of those articles, and other articles I have read recently refer to 12 March 2025 but I have not received any notification of changes over the last year until the email that turned up in November. I have posted a ticket asking for specification of these changes to which I have not received replies to my ongoing questions. Did this really did happen back in March 2025? I have to develop and deploy a new version of all my applications ridiculously quickly to a specification which is emerging only recently and in gradual stages. At present each day brings new information expanding the scope of the changes. Why has there been no newsletter to developers explaining all this apart from the very vague "Update to the MYOB Developer Program Terms and Conditions" email that arrived on 19/11/2025 which hinted at changes we might need to make by March 2026. Edge appearing without warning after repeating online authentication Since the changes to the Authentication process back in August 2024 I have found that going through the process of authentication to permit my application to access an online file when that permission has already been granted results in Edge appearing on my screen, on top of what I am doing, with all its screaming news, ads and associated clickbait. My issue is that when someone is setting up an application intended to enhance the benefits of their accounting system, that is a massive and irrelevant distraction. When someone is setting up to use an application for the first time it is not unusual to think one might have missed a step and repeat it. Getting Edge in ones face in those circumstances would be quite off-putting. Does this happen to other users? WIll the next round of changes to the authorisation process, due in March with a specification only now starting to appear on-line also address this issue/bug. Re: MYOB API Running Slow Today If not using invoice numbers, which is optional, we check for duplicate invoices by comparing customer and sale data including customers number if supplied, JournalMemo if supplied, ShipTo Address if supplied and CurrencyCode if supplied. TransPost will not import a sale if it matches exactly on all the criteria. A similar test is applied to other transaction types. In the latest version the same test is reapplied, after a pause, when retrying. The problem is working out just how long the pause has to be for this to be reliable. Today it seesm to have needed to be rather long. Re: Developer Communication - Issues Authenticating 3rd Party access to MYOB customer’s ledgers. I got in touch with the API Support team on 21st August, as soon as I realised there was a problem but apparently 2 weeks after the change was inmplemented with no notification. Tana's response suggests that they were blind-sided by this too so not much help there. It is clear they have little more knowledge about this change than us add-on developers. Talk about which browser one uses displays a complete ignorance of the fact that Windows applications do not use external browser apps to communicate over the internet. They can either use a browser control in a form or converse via GETs and POSTs etc. What has changed is the format/structure of the response. The specification of the change to that response needed to be published clearly many months before the change-over. Several weeks after this change we are finally getting an admission that the json response we had all been relying on for over a decade is not being returned. Also I completely fail to see why the response should trigger the launching of Edge. That is completely unnecessary and a hideous distraction. Re: C# WebBrowser -> WebView2 solution Interesting stackoverflow post. It might have been about using VB.NET but the code example was C# so I tried it out and got back a page of junk from MYOB which was a dreadful ad for the whole API concept, raving on and listing all the end points as if the recipient was a newby user who might be about to start developing an add-on. Certainly not stuff to throw at add-on users as if they were beginner developers. It possibly sheds light on the thinking behind all this. Zero has been rated as having better add-ons so someone in marketing, who has no idea what change management is, and thinks everything that comes in via the internet has a browser at the other end, has provoked this awful process round behind the back of those in MYOB who know anything about software and change management etc. It is the kindest theory I have been able to formulate so far! Re: Developer Communication - Issues Authenticating 3rd Party access to MYOB customer’s ledgers. I had it working for 3 of my 4 applications briefly and have been testing, as responsible developers do before deploying new versions. Today I find it is not working again so took a look at what came back from the request and found that far from it being a response providing the necessary oauth token and possibly a few other pertinent data items I had got back a page or so of a html ranting on about how wonderful MYOB was for small developers. If someone thinks that sort of thing is appropriate to shove in the faces of the clients of add-on developers whenever they install the add-on software on a new PC or for a new employee they should think again. It looks as though someone is of the impression that this authorization only gets applied when a fresh new developer starts up a new ad-hoc app for in-house use. I suspect that the perpetrators are probably unaware of how this is used and driven by some marketing/fashion motivation, quite unaware of any change management process. Myob is losing ground to Xero partly because Xero has a better range of add-ons. Breaking the existing add-ons is a long way from how to fix that. Could you please escalate this. It cannot just be fixed by linking to other developers discussions as to how to get round the problem. It is simply not acceptable to have add-ons being broken by ad-hoc changes without notice. The change management process should involve planning and notification well in advance, similar to the way it was managed for the upgrade to use TLS1.2 back in 2017, when we were given ample notice to enable us to prepare new releases. Re: Developer Communication - Issues Authenticating 3rd Party access to MYOB customer’s ledgers. Yes, I have benefitted from the advice given by Steve_PP but it is too much to expect him to keep on helping with on-going issues. He may have solved this problem and has helped a few of us to do so too but some of us do have on-going issues. I have just had to promise a user that their latest renewal will be extended to reflect the period that they cannot use our system. They will not be the only ones. That on top of not getting new sales until we have this solved. if MYOB were advised that the change would be transparent to all add-ons they perhaps did not understand what a variety of add-ons there are out there. Also such statements from people/organisations selling something need to be taken with a full handful of salt. Some testing would have been in order and roll-back immediate once the problem emerged. What they should have done is leave the existing structure/process in place, implement the new one via a different URL and notify all of us developers as to what they were doing and that they would be closing down the original after we all had sufficient time to adapt, say sometime next year. that would provide time for everyone both within MYOB and us developers to test in development, not on live systems. I still think this demonstates a shocking lack of proper change management process. Re: C# WebBrowser -> WebView2 solution I am still mystified as to why people keep on about IE versions and Edge. I am trying to make a WinForms app work and the relevant thing is what dlls are needed and how they are used, not what browser I, or my users, use. I suspect the issue is that the perpetrators did not understand that fact. I suspect that is an issue about where that //desktop redirect goes but the real meat is not that but the data that is returned. I have two apps that use the same code. One now works having disabled the error that arises from the redirect, but on my test PC as opposed to my development PC it launches Edge, quite unnecessarily as far as I can see. Can anyone explain what that redirect is meant to do? I have never understood that. There is no reason I can see why an actual external browser should come into it. The other app fails, despite using the exact same code (same source files!) The only difference, apart from addressing a wider set of end points which should not be relevant, is a different code and secret. Off to examine possible differences in their csproj files.