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
Calling a suitelet -- best practice
We have any number of scripts that call a suitelet. These have been in place for more than a decade. They call the suitelet using these lines of code:
var url2 = nlapiResolveURL('SUITELET', 'customscript179', 'customdeploy1', true);
var response2 = nlapiRequestURL(url2, null, null, null);
Starting with 2024.2, these stopped working. The first line returns a value into url2.The second line triggers an internal server error 500. My guess is that the value returned to url2 while looking correct, is no longer acceptable. Our consultant worked around the problem by setting the value of the URL explicitly although he said that this isn't the best way to do this.
Tagged:
0