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.
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.
Session and Login Issues with Password Protected web store
Here are a few issues I have found with session management in the webstore:
1. Login to a secure password protected web store and nlobjContext will contain the user's customer record ID. Logout and the context still contains the user's customer record ID. Clear cache and history, Close the browser, reboot your machine, relaunch browser and context still contains the user's customer record ID. This is not good if user's share same computer but login under different customer records.
-update: 2013-Mar-29: This is still true.
2. Login and use nlobjContext.setSessionObject to save a session variable. Logout and view nlobjContext.getSessionObject and the variable is empty (that's good). Log back in and view nlobjContext.getSessionObject and the variable contains the value from the previous session (that's bad).