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.
CSV Imports throwing Unexpected Error With New Release
Hello,
We were just upgraded to the new release with the new UI, and everything seemed to be fine except for our CSV Imports. We have some scheduled scripts that create CSV Imports to create Sales Orders, and on these CSV Imports there are registered trademark symbols. The CSV Imports they are using, use the Western(Windows 1252) encoding and have worked fine until the new release.
Now, they throw either an unexpected error, or fail to import because it cannot recognize the registered trademark symbol. The weird thing is that if I run the CSV Import manually with the same CSV file and same CSV Import, the orders import correctly and does not complain about the registered trade mark symbol. I think it has something to do with using the nlapiSubmitCSVImport function in suitescript and the new release. It seems like it may automatically be converting the encoding to UTF-8 or something else on the CSV Import it is using. I wanted to see if anyone