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
Bug in Custom Buttons in 2013.2
So I've got a weird issue happening. We've got a set of 4 custom buttons on our Sales Orders that are scripted to do different things (make a special PDF, run a related search, etc). The top copy of the 4 buttons all work correctly. In the bottom set of buttons, two of my 4 buttons are causing the same action to fire. As far as I knew, the top buttons and bottom buttons are supposed to be exact duplicates. I certainly haven't programmed them in separately.
I have no idea what to do about this, except to tell people to use the top set only for the time being. Does anyone know what this could be? I'm believing that it's related to 2013.2 since it just cropped up, but it could have been doing this prior to our upgrade and just went unnoticed. It's doing the same thing in different browsers, users, records, etc., so it's not a caching issue of some kind.