Update on this issue – now affecting 340 contacts and growing
Posting an update because this problem has escalated far beyond what was originally reported.
When I first raised this, the issue only seemed to affect contacts alphabetically after a certain point in the list. That was already concerning — but the situation has now significantly worsened.
This is a growing and unpredictable issue that directly impacts:
Every day, more contacts become undiscoverable through standard search in sales screens, which effectively cripples core functionality.
This needs to be recognised as a high-impact regression.
It is expanding over time and affecting a critical part of the software.
Please escalate to engineering for investigation into search/indexing behaviour at scale.
If anyone else is experiencing contact searches failing beyond a certain alphabetical point — especially when searching invoices, quotes or bulk email — please comment. Even brief confirmations will help MYOB understand the scope.
I'm experiencing this on MYOB online too. Any further feedback? Seems tablestakes.
Hi Earl,
Respectfully, this issue has already been raised with MYOB Support and escalated through the complaints/resolutions pathway.
The problem is that logging another support case does not appear to achieve anything meaningful when the underlying defect is already known, unresolved, and still not fixed after a very long period of time.
We’ve been waiting on a fix for this issue for over a year now. The issue affects the Customer field when searching existing invoices/quotes/sales orders, and it also impacts bulk email behaviour. It is not a browser issue, cache issue, or something MOCA is going to diagnose.
Brisbins can absolutely lodge a case so their account is linked to the defect, but let’s be realistic: MOCA is just a virtual assistant/support intake pathway. It is not going to resolve a backend/customer search regression that MYOB already knows about.
What would be more useful here is for MYOB to confirm publicly:
At this point, asking each affected user to individually go through MOCA/support feels like deflection rather than resolution.
Brisbins — I’d still recommend commenting here and lodging a case so MYOB can’t treat this as isolated. But based on our experience, don’t expect support to fix it directly. The issue needs product/development action, something which MYOB seems to only like doing selectively.
