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.
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.
Understanding nlapiGetNewRecord()
[h=2]The documentation for nlapiGetNewRecord() states:[/h] Available in beforeLoad, beforeSubmit, and afterSubmit user event scripts. This API never reflects any changes set by the system during the submit operation. It only reflects the field and line item (sublist) values submitted by the user.
Note that you are not allowed to submit the current or previous record returned by nlapiGetNewRecord(). Also note that only fields that are changed (submitted) will be available via nlapiGetNewRecord().
I assumed that this API would only reflect the fields that are changed, in other words the ones that you can see in the system notes as Changed via UI. But when I tried this API on an Inventory Item record manually changing just the value of one field, the fields object returned 387 fields. I also tried the following to compare: