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.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
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?