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
2018 WSDL missing legacy invoice address information
We are upgrading our solution from 2014.1 to the 2018.1 wsdl. Invoice had a string property called billAddress, but now has an Address type field called billingAddress. We have switched our soluton to utilize the billingAddress fields, but have noticed that sample data within our test accounts show billing address information in the billAddress field using the 2014.1 api, however, these same invoices accessed using the 2018.1 API return a null billingAddress. updating the address on the affected record fixes the data issue.
Other records created using the 2014 api, 2018 api, or the Netsuite UI appear to show the data correctly.
Should we be concerned that customers will see this issue with Invoice records created before a certain date, when our solution is updated.