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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
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