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 Question of the Week! You only have until tomorrow, November 6, 2025, 2PM 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

nlapiSetCurrentLineItemValue() - firefieldchanged not respected?

edited Dec 2, 2019 6:01PM in SuiteCloud / Customization 4 comments

Argh, been chasing down a bug for 3 hours now and it looks like it's actually a NetSuite bug.  According to the docs:

nlapiSetCurrentLineItemValue(type, fldnam, value, firefieldchanged, synchronous)

                                                        firefieldchanged {boolean} [optional] - If true, then the fieldchange script for that field is executed. If no value is provided, this argument defaults to true. (Available in Client SuiteScript only).

However the following code IS raising the validate event!
 nlapiSetCurrentLineItemValue(type, FLD.LIST_WOAMOUNT,       result.getAmount(), false);

Note the fourth parameter set to false.  When stepping through the code in FireBug as soon as this line executes my validation handler is called with the just-changed field.

Steve Klett | Senior Developer
NetValue Technology

image-8cb77df5036e1-7e7f.png

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 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders