Thank you for visiting our Partner Zone. This area is an exclusive space for MYOB Partners. Find out how to Partner with MYOB.
From CloverQ query (see this post, I'm moving the question to this forum) I'm getting upgrade errors going from 19.15 to 2019.1. We have multicurrency in the file.. and the error log I got has this:
2019-04-02 19:10:45.5593,MYOB.Huxley.UI.Controllers.Migrator.MigrateMyoFileController,Warn,1,Migrate Multicurrency File failed due to unsupported transactions
Scan finished in 29 seconds
Serial Number: xxxxxxxxxxxxxxxx
I'm not the accountant, just the IT guy but I can dabble in the file and can help them direct what needs to be done in the cleanup....
just going by this line:
Migrate Multicurrency File failed due to unsupported transactions
did you try upgrading online or offline? offline upgrades aren't supported yet, but online ones are. if you're able to upgrade online, you can still continue. otherwise I'd say @CloverQ needs to send you the deferral number for those who cannot upgrade.
From the looks of things it looks like this was attempted to be upgraded offline, in which case @sholt73 has linked you to the best post on this matter.
With that said, I have also sent you a Private Message with the STP Deferral Code for clients who cannot upgrade just yet. You can check your Private Messages by clicking link: Private Message Inbox
No this was a online upgrade.. offline upgrades refused outright due to multi-currency, online gave warning that some mutlicurrency may not work, but I gave it a try as I don't known what type of mutli-currency transactions we have.
So I have to wait for the next update to 2019 then. Looking at this page: http://help.myob.com.au/updates/multi-currency/ maybe I have one of those transaction type that are not convertable yet, but can MYOB tell me that all those transaction type will be really for upgrading in the next release? (and hopefully before 31/5?) (I'm not sure if our accountant use all the foreign transaction features that MYOB say are not yet supported in 2019, but far as I'm concerned I just want the data first in 2019, functionalty can come later).