MYOB EXO 2016.2 Release

24 June 2016 > General, Software, MYOB Exo,

MYOB EXO Business 2016.2 has now been released, and we have created a slightly shorter version of the 2016.2 release notes:

Features

New Purchase order Grid

Stock Search Templates available in new purchase order grid.

(However please note there is an issue with 2016.2, when you update the select qty from a stock search template for numerous stock codes it only brings through one).

Submit tax reports electronically from within EXO

The NZ GST Return can now be submitted to the IRD electronically. The NZ GST Return window includes new tool bar buttons for submitting the rpeot online and managing submissions

Clarity Report Print to File Options

The Print to File Setup window in the Clarity Report Designer has been redesigned, making it easier to produce XLS data files with properly aligned rows and columns from Clarity reports.

GL Trial Balance Tree Options

Additional new check boxes ‘Show inactive accounts’ and ‘Hide Zero Balance’

Display of Currency Symbols

E.g. €, £, ¥, are now displayed on all relevant common windows (DR & CR Accounts, PO & SO search grids)

Job Costing Date Validation

To better support perpetual inventory integration, validation has been added to the transactions dates.

Once a job has been saved, it is no longer possible to change a transaction’s date to one in a different period; the date can only be changed to one in the same period as the original date.

When entering transactions on the Quote/Budget tab of the Job Details window, the date defaults to the current date, unless you have not rolled over to the current period; in this case it will display the last date of the period you are currently in.

Extra Search Field Formatting

Enhancements to the user-level profile settings that add extra fields to the various search screens and grids that support them, e.g. Extra stock items search fields, Extra creditor account search fields. The formatting of extra fields added to search windows can now be customised;

Posting GL Ledgers from the Command Line

The Post Ledgers to GL function can now be run from the command line, allowing you to process the default ledger posting in a scheduled, automated, unattended mode out of hours. To run the posting process from the command line, run Exonet.exe with the /POST_LEDGERS flag, i.e.:

Exonet.exe <database> <username> <password> /POST_LEDGERS

Resolved Issues

When emailing invoices or statements from the Transaction tab of the Debtor Account Details window, the system did not use the Statement Contact specified on the Details 2 tab, if one was available.
When emailing invoices or statements from the Transaction tab of the Creditor Account Details window, the system did not use the Remittance Contact specified on the Details 2 tab, if one was available.
If the selected statement contact was unlinked from the Debtor account, the mailshot for Debtor statements or invoices would not use the correct email address.
When a new Contact was created from a Debtor account, the Delivery Address entered would be overwritten with the Postal Address. This has been resolved.
When Extra Fields were added to the Stock Search window, they would display decimal places as per the Quantities decimal place setting on the Essentials > General Settings of EXO Config. This has been resolved; the functionality of all of the various Extra … search fields profile settings has been extended to allow formatting to be specified.
When sending creditor remittance advices using the mailshot function no CLE file was selected by default, even if one was available, which meant that users had to browse to find the CLE every time they used the mailshot. This has been resolved.
Unnecessary document management prompts appeared when a user saved a Sales Order by clicking Save & Exit (but not when clicking Save). This has been resolved.
On the Bank Feeds window, the Hide Transactions button was initially greyed out until the view was changed. This has been resolved.
When a job line was cancelled, the GL transactions were always created in the current period, not the period in which the transaction originally took place. This has been resolved; users are asked to confirm a cancellation if the transaction’s period differs from the current period, and the period can be changed on cancelled lines if necessary.
When crediting a job invoice that included a retention, the retention value would be missing. This has been resolved.

Known Issues

Due to security settings imposed by Windows, CHM Help files cannot be viewed from a remote location—this means that you can only view the EXO Business CHM Help files if they have been installed on the local PC.

The stored procedure SP_DEMO_DATA_DATE_UPDATER, which updates the data in demo databases to the current date, was updated in EXO Business 8.4. This stored procedure is only available in the EXO_DEMO database, which means that any existing demonstration databases used by partners will not be able roll their demo data forward; these databases will need to be re-created based on the updated EXO_DEMO database in order to use the updated SP_DEMO_DATA_DATE_UPDATER procedure.

Job Costing Resource Issues - When a resource allocation is created, an Activity for the relevant staff member is automatically created in the EXO Business system; however, if the resource is not associated with a staff member, the Activity will not appear on the Activity Search widget on the Task Scheduler tab.

As a workaround, a dummy staff account can be created to associate non-staff Resources with.

SQL Server 2012 Issues

All versions of SQL server 2012 exhibited a subtle, but now well-known change in default behaviour with regard to identity or auto number sequences. In MYOB EXO Business, this would be experienced as an unexpected anomaly where number sequences could apparently spontaneously jump by increments of 1000 if the SQL server was restarted.

This behaviour was reversed in SQL server 2014, but no known solution exists for completely preventing this behaviour in any versions of SQL server 2012, other than to upgrade to SQL server 2014 to completely eliminate the potential for this issue to occur.
SQL Server 2008 R2 prior to SP3

MYOB EXO Business uses a SQL Server feature called Common Language Runtime Integration. This feature was disabled by default in versions of SQL Server 2008 R2 prior to Service Pack 3. If this feature is not enabled, users may encounter the following error during the upgrade process:

Updating server configuration: 'clr enabled'