Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Treat Warnings as Errors vs. address validation
I believe I read somewhere that Web Services users are encouraged to set the option "Treat Warnings as Errors" to true.
If I do so, I run into what seems to be draconian validation of addresses.
If there's no zip code, there's now an error: "Without a Zip/Postal code it will not be possible to use this address with 3rd Party shippers"
I also see "Without a Label it will not be possible to use this address with 3rd Party shippers" (not sure what a Label is in this context)
Did I misunderstand the intent of using this setting? Any downside to setting "Treat Warnings as Errors" to false?
0