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.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly 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.
Both ODBC and JDBC drivers stopped working on May 9, even with updated attributes
I am unable to connect to SuiteAnalytics Connect both via ODBC and JDBC connections. Has this happened to anyone else?
I'm stuck in NetSuite Support hell with a case that's not moving forward and its a significant impact to our business.
The last successful use of SuiteAnalytics Connect was Saturday, May 7th. Since Monday, May 9th, all of our data refresh processes, both automated and manual, have failed to connect to NetSuite. I traced it back to the ODBC and JDBC driver connections, which both return "TCP/IP error, connection timed out" errors.
I assume it is related to the "Required Update of SuiteAnalytics Connect Drivers" update (linked below), but I have updated all attributes and drivers according to the documentation. I've tested it on the work network and also my home network and receive the same error, reducing the likelihood of firewall interference.