Discussions
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.
Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
nlapiRequestURL and Asian header data
I am employing an afterSubmit user event script on Customer records that's meant to submit data to a web server we have running ASP. The script uses nlapiRequestURL() to post the data over SSL with HTTP Auth.
It works great on U.S. characters contained in our Netsuite customer records but when data gets sent over that uses international characters, they are replaced with question marks, indicating a character set issue.
I have verified that the web server and database on our end support Asian characters; as I can submit this type of data through a web browser.
I must be missing something in preparing the nlapiRequestURL call in order to support the international character sets. Can anyone shed some light on this?