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!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Different values for the same Transaction status
Chasing down a bug and finally had to resort to logging values to find the problem.
Here is some code first, then I will explain the problem.
// Here are some snippets of the values used below var TRANS_STATUS_LIST = { PEND_APPROVAL : 'A', PEND_FULFILL : 'B', PEND_BILLING : 'F' }; // BTW, transaction status field is 'orderstatus' but the searchfield for status is 'status' - this is the kind of junk that makes people go crazy! var currentSalesOrderStatus = nlapiLookupField(REC_IDS.SO, salesOrderId, TRAN_SRCH_FLD.STATUS); this.AddTraceF('Current SO status: {0}', currentSalesOrderStatus); if( currentSalesOrderStatus != TRANS_STATUS_LIST.PEND_APPROVAL ) { this.AddTrace('SO doesn't need processing, aborting operation'); return; } Steve Klett | Senior Developer
NetValue Technology
0