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.
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
Some nits on docs
OK, these are nits I'm sure but wanted to express just the same. With various times when APIs break because the parameter was not a string or not an Array (e.g. one thread here where we need to make sure the value is a string -- val.toString() ), it may be more important than not.
Inconsistencies:
- There are numerous APIs that require the RecordId to be passed. On some, this is identified as type Integer. On many others it is identified as type String. Although Javascript is loose typing, I still prefer to code as if it is strong typed -- just good practice. (compare nlapiLookupField and nlapiLoadRecord for example).
0