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
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).