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.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
No Limits. Just possibilities.
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.
Try Intelligent Payment Automation – Fee Free For Your First Month

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.
Community Articles: What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now and spark the next big discussion!

Problems with nlapiSetFieldText/Value

edited Jan 8, 2020 2:24AM in SuiteCloud / Customization 8 comments

Hi there!
Im having a wierd problem setting values to Dept/Class/Loc fields in a Sales Order.  At the Job level, we have already defined the dept, class and loc and I want this to get sourced when a SO is created.  I tried the nlapiLookupField and that didn't work.

So I created three custom body fields to source these values from the Job and have a post source client script to copy it into the std Dept/Loc/Class fields. 

The issue:
Both nlapiSetFieldText/Value work well only when the lists are a dropdown.  When the number of entries exceeds the Max entries in the dropdown (as per the user's preference) and the field become <type and tab>, the code breaks! nlapiSetFieldText add a "\" at the end and nlapiSetFieldValue does not work at all!

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 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders