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.
Connection timeout with Ruby script
When running a Ruby script using classes generated through wsdl2ruby (part of SOAP4r), the login is successful, but a subsequent search generates a SOAP fault complaining that the connection has timed out. The query is submitted immediately following the successful login. If the same steps are executed manually from within the Ruby interactive interpreter (irb), the login and the search are both successful.
Removing all of the flow control and error checking, the script boils down to this:
service = NetSuiteService.new
service.login(uid, pwd)
service.getFutureEvents
service.logout
NetSuiteService is a slim wrapper around NetSuitePortType generated by wsdl2ruby. Even if I replace it with direct calls to NetSuitePortType (as per the code below) from the script, the result is the same.