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
div__body being closed early in top-level categories?
I just re-designed my layout a little and for some reason the netsuite-generated div that contains the body is being closed only the the top-level categories of my "Shop" tab...
http://www.bestamericanarts.com/Shop/American-Handcrafted-Jewelry
Notice how in the above link the nagivation portlet is shifted to the bottom of the page... this is because there is a </div> tag that is closing div__body... now click one of the links to a subcategory or item drilldown... now it works perfectly.
I am 99% sure it isn't coming from my code - in fact both those pages are using the same item layout. This error is consistent across Firefox and IE as well. Please help... appears that the code is being generated directly after my Theme's "Content Template".