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.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
No Limits. Just possibilities.
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.
Try Intelligent Payment Automation – Fee Free For Your First Month

Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.

The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.

For more information, visit this thread.

2018 WSDL missing legacy invoice address information

edited May 26, 2020 12:46PM in SuiteCloud / Customization

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.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders