The_Doc
Ultimate Cover User
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Cannot get Authentication to work on Windows Forms Desktop app
Hi DavidK3 Have you sorted your problem - Mike James gave some good pointers! Likely I can help though most of my apps are based on MSAccess and this is really easy to fault find during development. However I did then create a vb.net and vc.net test app successfully get my codes after the MYOB token server crash - reasoning - so I can sort for myself the problems. Likely you are getting something back on your callback but not looking in the right place - as of the crash it is no longer embedded in the returned page but the returned url. The red herring re the requirement for you to use a webbrowser2 was just that - a red herring - it wasn't the problem. All my Access apps run perfectly without using a WebBrowser2. Interestingly, XERO token codes creates an error in my MS Access trial app as "this browser is outdated" - but if I set errorflag=true to turnoff warning - I still get my codes without problem. Regards The DocRe: Importing tracking into invoices
Hi melissa2017 From my understanding of existing invoices - you cannot patch edit them - so unless you added this to the comment field - or an item called 'tracking' at the time the invoice is created then your task becomes much harder. There is a way around this as I had to do this with an invoice with backorders on item(s) - I created an order with just 1 line. eg. the parent was called WebRP00123567A2 - meaning 2 BackOrders exist. The BO is give a B1,B2 etc suffix. When the order on the item is filled - I just delete this order and create a new invoice with the item in place - works well. No editing - I think the theme could work for you with tracking. Just a thought. The DocService Invoices Downloading doubling
Hi Folks Thought I would post as a head's up until I get an answer from API support. A client posted a query that a Job Costing package was giving errors on some jobs but not all. I wrote the package in MS Access in about 2013 for AccountRight 19.16 with ODBC - then 2016 ( or around there) - local file - then upgraded it to an online file. Most, if not all faults have long been ironed out and it works and I hear very little from them. Except mid Sept - suddenly I am getting a double up in $ figures on some invoices and some jobs. Whilst I ALWAYS work from the frontend back and never assume there isn't an odd code bug ( 99.9%) are removed. I am suddenly getting a double up in service invoices downloaded - I use page=1000. The download takes 2 pages - and there is a doubling up of some invoices - the OData extract is doubling up - grrr I captured to json page downloads and looked for a doubled up invoice and it was on both pages. UID for the record were identical so it is the same entry but grabbed twice. Awaiting MYOB's API support reply. - you may well ask why I haven't turned on a primary key ( no duplicates) - because sometimes duplicate invoices do exist for a reason. However, I do not capture UID - but I need to spin up a quick solution whilst MYOB ponder this problem. I will make this a primary (no duplicate key) and loop to the next entry so we can get around this apparent problem. Just giving a heads up to check folks. The DocRe: MYOB API Running Slow Today
Hi Steve_PP Thanks for the input - food for thought - can't say I have a figure for fail but it 'seems' that it is easier to assume it hasn't been inserted and go around again as my invoices are quite complex and I don't store a backup format of the invoice to be able to run again. Not sure how I am going to handle it, but it is good sleep material or running fodder - since posting my invoice numbers are unique and should not be duplicated - but having said that I can download item invoices, but this just adds another big payload to just check whether invoice numbers are duplicated. At present downloading Sales Orders (back orders) is a lumpy, problematic and prone to a lot of timeouts and is under investigation by MYOB API - so doing this with actual invoices to just get their numbers gives me chills - but I may not have any alternative - let me look at your suggestion and see if it will work. ThanksRe: MYOB API Running Slow Today
Yep - really annoying - something that takes 11 mins - downloading of BackOrder invoices - took 46 mins - yes there are error loops to catch but I have had to broaden these in the last month trying to resolve appalling download times for BOrder invoices - grr ..... However, the reason I posted was a very annoying thing that I am not sure how to fix - if I post an invoice or a BackOrder - something that 'does occur' but today it has happened too many times - [ and yes I know if you turn on - 'warn if duplicate invoice numbers' - this will error your post so I turn it off ] - but when MYOB has another one of its 'Gateway timeouts' - an invoice can actually get through and be posted successfully but we still get a 'gateway error' - so my code says - 'ok try again to post' and you get a double up. Apart from turning on 'duplicate invoice number warning' - anyone know a way to PREVENTING' I am doing a mind exercise at the moment trying to consider so coding to check this?? The DocRe: How to handle deleted invoices through the API
Hi dkarzon-pinch Have a look at the pointer from Mike_James - however, I have developed an app for a client that has now taken over backorders in their MYOB system - and invoices get added and deleted all the time especially SOrders. And I also delete them from my app. Each invoice has a URI - as does each SO - however, in my initial build of my app I struck this problem and built a copy in my app of all invoices in myob - and cross checked this everytime I updated - and produced an error code if an invoice had vanished - I think this is your simplest way - invoice id are not unique enough but uri are and are only accessible via the API. My system works ( actually if I get a duplication of an invoice/SO number it causes a problem but that is by design - not as a fault) - but for the MYOB API to delete an invoice or SO it is very easy - it just needs the uri - which for duplicate invoice numbers or SOs are unique. Hope this helps but it is a relatively easy solution to code. The DocRe: Update on 3rd Party App error connecting to MYOB AccountRight.
Hi UmeshP What problems arre still having - are you using the MYOB SDK in VB.NEt or VC#.NET. I posted some info and have been in constant comms with Tana - and I believe, as she has agreed, that the browser type was a red herring - i.e. MYOB just didn't know the problem, or understand it. I am mainly a MS Access database user - and developed ( as all MS Access developers do) our own code dispensing with the MYOB SDK. However, I am also a developer of apps ( which doesn't connect to MYOB) and I write in VB.Net and Vc#.Net. I dug out the old VB.NET code MYOB produced in 2013 to get new developers to MYOB APIs a leg-up on access to the API - i.e. it made it easy to 'get going' - but that utility is no longer available. I found an old copy dated 2013 on my server and actually got it going without any more that 2 lines of updated code. I couldn't find the VC#.Net version but coding is very similar. Steve_PP highlighted the VC#.Net solution. The summary to all of the above is that "The browser type didn't matter" and I suspect it never will - and I have no intention of paying the AntView2 fee for the wrapper version for MS Access. So if you are still having problem I suspect this is not because of MYOB ( not that I am letting them off the hook - they made a mess of the changes) - what I am saying the changes that did happen ( that MYOB didn't understand) - were actually relatively minor and simple code changes ( in the end) got us back on line. The future proofing is - knowing that MYOB drops bombshells without knowing their effect - aint that a developer's lot. The DocRe: JobRegister queries
Hi MarshallArts I work differently to you with Endpoints - why - because I don't use the MYOB SDK where all the data is extracted via Abstract Methods - you get to see whatever MYOB decides. I write my own extractions - so I use Endpoints to get me a page of JSON data - then I decide whether the info I need is in that endpoint - payroll is a good example - there is no payroll endpoint that will give you all payroll data - but mix and match different endpoint including GeneralLedger and it all comes together. Here is an extract of a JobRegister endpoint - but you would need a copy of theJobRegister from before the suspected change. Then you could compare them. You need to do a bit of Sherlock Holmesing to work out what has changed then work backwards into the SDK to see where it has changed. Sorry, I can't be more helpful - but the way I extract data from endpoints is coding more intensive but I remain fully in control of the data I need. The DocRe: Developer Communication - Issues Authenticating 3rd Party access to MYOB customer’s ledgers.
Hi Mike_James Yep have to agree with you both - a dismal mess by MYOB on the par with CrowdStrikes mess. I think @MikeJames is onto something regarding a 3rd party IAM taking over MYOB's security tokens - the addition of the prefix "ory...... to the codes and tokens seems to be the beginning of this mess. Like @Mike_James I am not a primary .Net user for access to MYOB's API so fixes from the API forum (mostly .Net based) aren't useful to us per se, however, since this mess rolled over us I have brought up to speed the old 2010/2013 VB.NET API SDK MYOB utility - updated and got it working so that I can now keep abreast of MS Access & VB.Net changes. However, in the end as @Julia alludes to the browser change was a red herring and in fact, in my opinion, MYOB darting up the wrong tributary for the source of the problem - it was the format of the returned payload that had changed AND the token format because it was either being created by a 3rd party IAM www.ory.sh or the change wasn't the browser but the whole internal token producing code - we will never know. The end result was simply us developers were treated as 2nd rate citizens and the changes were dumped on us without out due process, consideration or thought which suggests something deep within the bowels of MYOB went wrong and some collective rear-ends need re-assignment. See my separate post yesterday but in the end the fixes to MS Access code and VB/VC#.Net codes was simple and likely would have been worked out quickly by the collective brainpool that this forum provides. The failure was "WE WERE JUST NOT TOLD" and then lead on a wild goose chase regarding browser type - sure this might ultimately lead to some more adjusting of our code but it was NOT the critical change that brought the camel down. Wake up MYOB - we developers are a critical mass and such disasters do you a lot of damage. The DocRe: JobRegister queries
Hi MarshallArts I cannot directly answer this as I don't use the SDK to access their endpoints - for the reason that you are at their mercy to how the code works for accessing endpoints. I have a client using jobs, sub jobs etc - and I can have a look at a page extracted from the endpoint as post it to you - it should then give you perhaps a bit more info about your query. The other thing you can do - simply code up a simple form in VB.NET with the jobsregister endpoint to see the json payload you get back - it should help you further. Re my client - I may not extract the data to the depth you do from the jobs register but my client hasn't had any problem - and jobs are extremely important in my package. The Doc
