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.
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
errors with nlapiResolveURL?
I figured as long as I was writing a note to support I'd try picking the forum's brains as well. Basically I'm trying to call nlapiRequestURL() to hit a CGI script on the server. Because there's some kind of character limit on how long that string can be we're opting to try and pass the data as headers. We know that this is at least possible as we've done it once before in another script. So my question becomes, is there some reason why nlapiResolveURL would work in a library script but NOT in a User Event onSubmit function?
I do manage to get a line of debug (the first nlapiLogExecution call below) from directly before I attempt to fetch the URL, but I get an unexpected error on the line when I do.
0