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.
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.
NetSuite launches new wholesale distributions solution in Japan in January 2026!

NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.

Register Now
NetSuite 2026.1 Release Notes - This document summarizes the changes to NetSuite between 2026.1 and the previous release.

Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.

Calling a suitelet -- best practice

edited Jun 2, 2025 2:49PM in Ask A Guru 3 comments

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.

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