Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
transactionShipAddress on CashSale
We had long been setting transactionShipAddress on CashSale from web services, primarily to prevent any defaulting behavior, but at some point in the last few days, on Monday I suspect, we started getting errors. This caused a significant disruption of our business, and required emergency fixes to several of our internal applications. I don't believe any forms were modified by us in that timeframe. I'd very much like to understand why this happened when it did, and if there is documentation somewhere of the change that was overlooked. Was this a breaking change masquerading as a "bug fix"?
ERROR:INSUFFICIENT_PERMISSION You do not have permissions to set a value for element shipaddress due to one of the following reasons: 1) The field is read-only; 2) An associated feature is disabled; 3) The field is available either when a record is created or updated, but not in both cases.