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.
Don't miss out on our Pop Quiz You only have until November 18, 2025, 2:00PM ET to comment your answers and earn rewards! Click here for more details.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
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
Migrating SOAP to REST
Hello!
I am currently looking to migrate from SOAP to REST having heard in the latest release webinar that there is parity between the two.
Some roadblocks I've run into - I'd just like to clarify what is the expected behaviour / best practices are with using REST in place of SOAP.
- I am looking to read many Vendor Bills, and within these bills I need all fields including calculated/non-stored fields. SOAP returns these fields. SuiteQL allows the querying of stored fields but not non-stored. REST seems to allow reading a single bill in this way, but not a long list unless you follow HATEOAS links (which seems like it could quickly cause rate limiting).
Tagged:
0