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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
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
accessing script parameters...
In the 2007 release, it looks like the following no longer works for accessing script parameters???
if (custscript_case_debug == 'T')
nlapiLogExecution ('DEBUG', 'Debug mode is turned on');
Now the following must be used:
var value = nlapiGetContext().getSetting('SCRIPT', 'custscript_case_debug');
if (value == 'T') {
nlapiLogExecution ('DEBUG', 'Debug mode is turned on');
I still see script parameters being accessed the old way in the docs/guides, so I am assuming I was not doing something wrong to begin with.
If this change is intentional (and I do like this new way much better), shouldnt there be a time where both ways work in order to update all scripts that are currenly in production???
0