Thank you for visiting our Partner Zone. This area is an exclusive space for MYOB Partners. Find out how to Partner with MYOB.
December 2021
December 2021
Since the upgrade to MYOB Essentials, when allocating transactions from a list of "unallocated transactions", a refresh of the list no longer occurs each time a transaction is allocated.
The most obvious "problem" this creates is when you are trying to do a transfer between two unallocated transactions. After allocating one of them, the second will remain unallocated until you refresh the list of transactions which gives the impression the transfer has not worked. Previously if you allocated either of the unallocated transactions in a transfer to another unallocated transaction, both would automatically be removed. The less obvious "problem" is that once an allocated transaction is allocated to an account code, it remains on the list until a refresh is done which when the list is long involves having to scroll down to find the remaining unallocated transactions.
Why is it necessary to have to refresh the list of unallocated transactions to confirm they have been allocated?
Solved! Go to Solution.
December 2021
December 2021
Hi @poko
Thanks for your feedback. This occurs more frequently during matching a transfer in order to ensure the transactions are properly matched as one transaction has already been allocated. That said, I understand your concerns regarding having to refresh the bank feeds window and have passed on your comments to the development teams.
Please feel free to post if you further suggestions or queries.
Kind regards,
Komal
MYOB Community Support
Online Help| Forum Search| my.MYOB| Download Page
Did my answer help?
Mark it as a SolutionHelpful? Leave a to tell others
December 2021
December 2021
Thanks @Komal_S.
I do hope the development team look at this, as unless it was a conscious design decision NOT to refresh the list each time an unallocated transactions is allocated, this should have failed regression testing during the build for the upgrade. I personally can't see how it is correct behavious that a transaction that has been matched continues to appear on the list of unallocated transactions until the user does a manual refresh.
Regards, POKO.
9
|
407
|
|||
1
|
172
|
|||
12
|
767
|
|||
3
|
366
|
|||
10
|
625
|