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.
Hi Earl,
thanks for the response. I've followed your advice and lodged a support case so my account is linked to the defect. As dbarkho notes though, this appears to be a known regression already under active cases with MYOB — so I'd echo the request for some public confirmation that this is owned by product/development and has a scheduled fix.
Happy to engage support in the meantime, but it would give affected users a lot more confidence to know this is actually in someone's queue.
Thanks.
Hi Brisbins,
Thanks for following up, and for confirming you’ve already lodged a support case.
I completely understand the request for public confirmation that this is in the right queue. From the forum side though, we’re not able to confirm internal product or development workflows, or provide commitments around scheduled fixes.
As you’ve already raised a support case, the best next step is to continue working with support directly so your file and examples stay linked to the investigation. We’re not able to confirm internal ownership or timing from the forum, but support is the right team to keep this moving.
Regards,
Genreve
