Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
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.