Will_H
MYOB Moderator
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: Clarification on SMS - 2FA requirements
Quick clarification for any Enterprise Division customers reading this. Requirement for SMS to be an available authorization method does not apply to MYOB Acumatica or MYOB Exo Business users. With that said, as someone who has to worry about customer account security, I encourage everyone to use App Based authenticators where possible, as these are most secure. In terms of cyber security threats, App authenticators are safest, SMS is technically easier to intercept, and Email is the least preferable option. The reason is that often if a bad actor has access to your computer they also have access to your emails, but they probably don't have access to your phone. Coupled with it being relatively easy to breach email accounts.Re: Exo Business - Conversion failed when converting date and/or time from character string. - September dates - New Zealand - Windows 11 & Windows Server 2025
Full instructions for changing Windows Language settings are here: Change the Windows regional settings to modify the appearance of some data types in Access databases. You can change your Windows language/regional format settings at: Go to Home and search for "Region settings" In the Region Settings screen, change "Regional format" to "English (Australia) rather than "English (New Zealand)" or "Recommended"Exo Business - Conversion failed when converting date and/or time from character string. - September dates - New Zealand - Windows 11 & Windows Server 2025
We're aware that New Zealand users of Exo Business may experience issues with their software when dealing with September dates. These are most obvious in the Sales Order screen where attempting to save a sales order with a September date will generate the message: Conversion failed when converting date and/or time from character string This is due to a change to Windows Regional Date Formatting, and how it manages the September short month name. Workaround: Change regional format to "Australia"Re: EXO Demo database SQL backup
Hi Phocas , I would recommend getting your customer's implementation partner to send you out a copy matching to the version in use at their customer. There can be some pretty big changes between schema versions over time (Notably, big changes to unicode handling in the 2020 release), and as an on-premise based product a lot of customers can be using versions that are quite a lot older than the latest.Re: Adding new Custom Table Schema with MySQL
Hi MadelCorvera, Development should definitely be done against MySQL databases in order to keep functionality as close as possible to production MYOB Acumatica instances. Can you confirm: What version of MySQL have you got installed? What version of MYOB Acumatica have you got installed? What screen(s) are you seeing the above behavior in? What error are you actually receiving and when? Please note: I can't offer full support via this channel, full assistance should be via your implementation/support partner's usual channels.Re: How to Create new table and a CRUD screen
Hi amhernandeza You can find a few youtube tutorials online for that kind of question, but really if you want to create that kind of screen I recommend doing the full Acumatica developer training, it's available free at: https://www.acumatica.com/acumatica-developer-training/development/Re: can someone assist , we are struggling to overwrite bom pricing that is set in exo via api
Hi Peterdms , You've mentioned EXO, so I'm guessing you're an Exo Business customer? You'll be best off taking this to your implementation partner if so, as Exo is so customizable I can't promise a definitive explanation of how your system works. There are various pricing procedures and methods interacting in Exo, so you really need someone with knowledge of your exact environment to get a full answer.Re: Custom Form Allow Access to People User Licence
Hi mauritz , Almost all licensing restrictions are defined by the namespace the report is sitting in. I'd generally try changing the ScreenID for the report to something closer to the Payroll Space, eg: MPXX1001 Where XX is standing in for your chosen development house ID.
