2020.5.7 Hot Fix Release Notes
Introduction
The 2020.5.7 release addresses issues that were identified in previous releases of MYOB Advanced.
This information is also available as a PDF document:
Resolved Issues
Finance
Problem ID | Description |
172961614518 173920302281 173806436121 173733720691 172974702351 172944342511 | When using a tax code with 100% GST on the Landed Cost screen (PO303000), the tax amount was calculated incorrectly. This has been resolved. |
- | In some cases, on the Validate Customer Balances screen (AR509900), the validation process executed starting from a certain period for a customer could incorrectly recalculate balances of payments and credit memos. This has been resolved. |
Order Management
Problem ID | Description |
- | It was not possible to create an invoice for a shipment after the originating invoice of the shipment with the zero balance was cancelled using the Cancel Invoice action on the Invoices screen (SO303000). This has been resolved. |
- | On the Shipments screen (SP302000), if the unit of measure of a package split line specified in the Contents of Selected Package table of the Packages tab differed from the unit of measure of the related line specified on the Document Details tab, the system did not recalculate the unit price of the package split line for its unit of measure, which could result in incorrect amounts of invoices. This has been resolved. |
Payroll
Problem ID | Description |
CE00017269 CE00017258 CE00017261 CE00017263 CE00017267 CE00017270 CE00017271 CE00017272 CE00017274 | The error message “Unable to determine the financial period for given date” could appear when processing a termination in a pay run. This has been resolved. |
System and Platform
Problem ID | Description |
CE00016653 CE00016628 | This release resolves an issue that prevented importing budgets via the API. |
- | When a new restriction group was created on the Restriction Groups screen (SM201030) and a customer was added to the group, the corresponding business account was not added to the restriction group. This has been resolved. |
- | If there were a lot of files available for synchronisation when the File Synchronisation screen (SM202530) was opened, the following error was shown: “The page was not displayed because the request entity is too large”. This has been resolved. |
- | The error message “Nullable object must have a value” when a row was selected on the Send Reports screen (SM205060) and the Process button was clicked. This has been resolved. |
- | Business events that should be triggered by changes made to existing projects on the Projects screen (PM301000) were not triggered if a MySQL database was used. This has been resolved. |
Integration
Problem ID | Description |
- | Product images failed to sync with BigCommerce due to BigCommerce rejecting non-secure HTTP links to the product images. This has been resolved; the links to be synced have been configured to use HTTPS to avoid rejection at the Commerce connector. |
Service Management
Problem ID | Description |
- | On the Appointments screen (FS300200), if a user added a line with the Service line type on the Details tab without saving, then added a line for the service on the Log tab, the value in the Duration column on the Log tab was not equal to the value in the Actual Duration column on the Details tab. This has been resolved. |
- | In environments with a large amount of data, the error message: “Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding” could appear when a user opened a document on the Service Billing Batches screen (FS305800). This has been resolved. |
