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 7, 2025, 2:00PM ET to comment your answers and earn rewards! Click here for more details.
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
Is this a bug? nlapisubmitfield and user event
I have a scheduled script that submits a single field, per record, using nlapisubmitfield. I chose nlapisubmitfield to keep the script running quickly and to keep the usage low.
I also have a user event script that runs on this record, before submit. This user event script pulls data from multiple fields, and updates another field.
The problem is that when i use nlapisubmitfield on the saved search, the user event gets null for all the other fields. When I changed my saved search to load the entire record, then submit it, the user event works fine.
This has to be a bug, right? Shouldn't the user event either get the correct values, or simply not run at all after nlapisubmitfield?
0